Add scopes(permissions) for the idv claim management API

[AfraHussaindeen]

Proposed changes in this pull request

Proposed changes in this pull request

• $Subject
• Related issue : Integrate Identity Verification for Identity Server product-is#15730
• Related PR : Add permission and scopes for the idvp feature #5989

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 40.16%. Comparing base (4c16f49) to head (278ba34).
Report is 10 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #6000      +/-   ##
============================================
+ Coverage     40.14%   40.16%   +0.02%     
- Complexity    14168    14170       +2     
============================================
  Files          1734     1734              
  Lines        116950   116973      +23     
  Branches      20027    20027              
============================================
+ Hits          46952    46988      +36     
+ Misses        62776    62766      -10     
+ Partials       7222     7219       -3     

Flag	Coverage Δ
unit	23.93% <ø> (+0.03%)	⬆️

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.