Add support for claim-wise uniqueness validation

[AfraHussaindeen]

Purpose

Introduce first-class support for attribute uniqueness validation.

Changes to the UI:

A new dropdown will be added to the attribute configuration section under the General tab, giving administrators the flexibility to define the scope of uniqueness validation for each attribute. The dropdown will offer three options:

• None: No uniqueness validation.
• Within Userstore: Validation applies only within the selected user store.
• Across Userstores: Validation is enforced across all user stores.

Note : This dropdown will be displayed only when the uniqueness validation feature is enabled via the deployment.toml

[identity_mgt.user_claim_update.uniqueness]
enable = true

Related Issues

• Improvement for Attribute Uniqueness Configuration product-is#21507

To be merged after

• Add support for claim-wise uniqueness validation carbon-identity-framework#6113

Updated UIs

IS/Asgardeo :

• Claim's basic details edit section includes a dropdown to configure the uniqueness validation

IS only :

• The claim's additional property section restrict the addition of isUnique property.
  • When the claim uniqueness valdiation feature is enabled

• When the claim uniqueness valdiation feature is disabled

Asgardeo only :

• Aternative login identifier improvement

Checklist

• e2e cypress tests locally verified.
  https://github.com/wso2-enterprise/asgardeo-tests/pull/2779
• Manual test round performed and verified.
• UX/UI review done on the final implementation.
• Documentation provided.
  Add documentation for the attribute uniqueness validation configuration docs-is#4911
• Relevant backend changes deployed and verified
  Add support for claim-wise uniqueness validation carbon-identity-framework#6113
  Add UniquenessScope as a first class property for claim management identity-api-server#741
• Unit tests provided.
• Integration tests provided. - N/A

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines
• Ran FindSecurityBugs plugin and verified report
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 32.32%. Comparing base (849c07f) to head (32fec6a).
Report is 293 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7106      +/-   ##
==========================================
+ Coverage   32.02%   32.32%   +0.30%     
==========================================
  Files          41       42       +1     
  Lines         893      897       +4     
  Branches      220      221       +1     
==========================================
+ Hits          286      290       +4     
- Misses        557      587      +30     
+ Partials       50       20      -30     

Flag	Coverage Δ
@wso2is/core	32.32% <100.00%> (+0.30%)	⬆️

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

Files with missing lines	Coverage Δ
modules/core/src/models/claim.ts	100.00% <100.00%> (ø)

... and 8 files with indirect coverage changes

[wso2-jenkins-bot]

🦋 Changeset detected

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.