Add service layer to manage authorization details types

[VimukthiRajapaksha]

Proposed changes in this pull request

This PR adds CRUD operations to manage Authorization Details Types, allowing for Create, Read, Update, and Delete operations.

• Implemented database layer and queries to support the new CRUD operations.
• Developed new services for managing Authorization Details Types within the framework.
• Created unit tests to ensure the functionality of the new features.

Related Issues

• https://github.com/wso2-enterprise/asgardeo-product/issues/22821

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.

[CLAassistant]

All committers have signed the CLA.

[codecov]

Codecov Report

Attention: Patch coverage is 67.98780% with 210 lines in your changes missing coverage. Please review.

Project coverage is 40.78%. Comparing base (ccb6562) to head (9d933ed).
Report is 6 commits behind head on master.

Files with missing lines	Patch %	Lines
...ntity/api/resource/mgt/util/FilterQueriesUtil.java	49.57%	51 Missing and 8 partials ⚠️
...ication/common/model/AuthorizationDetailsType.java	0.00%	36 Missing ⚠️
...t/dao/impl/AuthorizationDetailsTypeMgtDAOImpl.java	80.81%	27 Missing and 6 partials ⚠️
...application/mgt/dao/impl/AuthorizedAPIDAOImpl.java	81.20%	20 Missing and 8 partials ⚠️
...CacheBackedAuthorizationDetailsTypeMgtDAOImpl.java	75.86%	9 Missing and 5 partials ⚠️
...entity/application/common/model/AuthorizedAPI.java	0.00%	10 Missing ⚠️
...cation/mgt/AuthorizedAPIManagementServiceImpl.java	60.86%	6 Missing and 3 partials ⚠️
...rce/mgt/dao/impl/APIResourceManagementDAOImpl.java	69.56%	5 Missing and 2 partials ⚠️
...identity/application/common/model/APIResource.java	0.00%	6 Missing ⚠️
...identity/application/mgt/dao/AuthorizedAPIDAO.java	0.00%	3 Missing ⚠️
... and 3 more

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #6073      +/-   ##
============================================
+ Coverage     40.65%   40.78%   +0.13%     
- Complexity    14411    14510      +99     
============================================
  Files          1760     1767       +7     
  Lines        117611   118060     +449     
  Branches      20263    20293      +30     
============================================
+ Hits          47809    48147     +338     
- Misses        62520    62615      +95     
- Partials       7282     7298      +16     

Flag	Coverage Δ
unit	25.07% <67.98%> (+0.22%)	⬆️

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.

[sonarcloud]

Quality Gate passed

Issues
9 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.1% Duplication on New Code

See analysis details on SonarCloud