Removing application_type and response_type from DCR API model

[Ashi1993]

Proposed changes in this pull request

This PR remove application_type and response_type from DCR API model hence these parameters are not processed or stored in IS.

Related issue : wso2/product-is#21097

When should this PR be merged

[Please describe any preconditions that need to be addressed before we
can merge this pull request.]

Follow up actions

[List any possible follow-up actions here; for instance, testing data
migrations, software that we need to install on staging and production
environments.]

Checklist (for reviewing)

General

• Is this PR explained thoroughly? All code changes must be accounted for in the PR description.
• Is the PR labeled correctly?

Functionality

• Are all requirements met? Compare implemented functionality with the requirements specification.
• Does the UI work as expected? There should be no Javascript errors in the console; all resources should load. There should be no unexpected errors. Deliberately try to break the feature to find out if there are corner cases that are not handled.

Code

• Do you fully understand the introduced changes to the code? If not ask for clarification, it might uncover ways to solve a problem in a more elegant and efficient way.
• Does the PR introduce any inefficient database requests? Use the debug server to check for duplicate requests.
• Are all necessary strings marked for translation? All strings that are exposed to users via the UI must be marked for translation.

Tests

• Are there sufficient test cases? Ensure that all components are tested individually; models, forms, and serializers should be tested in isolation even if a test for a view covers these components.
• If this is a bug fix, are tests for the issue in place? There must be a test case for the bug to ensure the issue won’t regress. Make sure that the tests break without the new code to fix the issue.
• If this is a new feature or a significant change to an existing feature? has the manual testing spreadsheet been updated with instructions for manual testing?

Security

• Confirm this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
• Are all UI and API inputs run through forms or serializers?
• Are all external inputs validated and sanitized appropriately?
• Does all branching logic have a default case?
• Does this solution handle outliers and edge cases gracefully?
• Are all external communications secured and restricted to SSL?

Documentation

• Are changes to the UI documented in the platform docs? If this PR introduces new platform site functionality or changes existing ones, the changes should be documented.
• Are changes to the API documented in the API docs? If this PR introduces new API functionality or changes existing ones, the changes must be documented.
• Are reusable components documented? If this PR introduces components that are relevant to other developers (for instance a mixin for a view or a generic form) they should be documented in the Wiki.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 56.31%. Comparing base (4e516a5) to head (34a78a2).
Report is 7 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #2693      +/-   ##
============================================
+ Coverage     56.18%   56.31%   +0.13%     
+ Complexity     8636     8589      -47     
============================================
  Files           654      654              
  Lines         49129    49258     +129     
  Branches       9817     9917     +100     
============================================
+ Hits          27601    27739     +138     
+ Misses        17586    17570      -16     
- Partials       3942     3949       +7     

Flag	Coverage Δ
unit	39.50% <ø> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jenkins-is-staging]

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/13115834283

[jenkins-is-staging]

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/13115834283
Status: failure

[jenkins-is-staging]

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/13115834283

[jenkins-is-staging]

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/13115834283
Status: failure

[jenkins-is-staging]

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/13173239062

[piraveena]

[INFO] 
[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR] org.wso2.identity.integration.test.scim2.SCIM2PaginationTestCase.testUserListingPagination(org.wso2.identity.integration.test.scim2.SCIM2PaginationTestCase)
[ERROR]   Run 1: SCIM2PaginationTestCase.testUserListingPagination:125->getCurrentUsersCount:282 » AxisFault
[ERROR]   Run 2: SCIM2PaginationTestCase.testUserListingPagination:125->getCurrentUsersCount:282 » AxisFault
[INFO] 
[ERROR] org.wso2.identity.integration.test.scim2.SCIM2PaginationTestCase.testUserListingPaginationWithoutParams(org.wso2.identity.integration.test.scim2.SCIM2PaginationTestCase)
[ERROR]   Run 1: SCIM2PaginationTestCase.testUserListingPaginationWithoutParams:157->getCurrentUsersCount:282 » AxisFault
[ERROR]   Run 2: SCIM2PaginationTestCase.testUserListingPaginationWithoutParams:157->getCurrentUsersCount:282 » AxisFault
[INFO] 
[ERROR]   JDBCBasedUserMgtTestCase.testInit:39 » UserAdminUserAdmin UserAdminUserAdminEx...
[INFO] 
[ERROR] Tests run: 3219, Failures: 3, Errors: 0, Skipped: 18

Test failures are irrelevant to this fix.

[jenkins-is-staging]

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/13173239062
Status: failure

[piraveena]

Failing with above 2 issues, and those are not related the this DCR fix. Hence merging this PR