[UI][next] Enhance pre-issue access token action V2 and user attribute management

[Lashen1227]

This pull request introduces support for versioned configuration and user attribute management in the Pre-Issue Access Token action. The main enhancements include adding user attribute selection for action versions beyond v1, updating the form and models to handle these attributes, and providing version-specific rule messaging and grant type restrictions. These changes improve flexibility and clarity for administrators configuring actions.

User Attribute Management:

• Added user attribute selection to the Pre-Issue Access Token action form for versions other than v1, including state management and submission handling for updated attributes. (pre-issue-access-token-action-config-form.tsx
• Extended action models and interfaces to support user attributes in the Pre-Issue Access Token action, including config, update, and response types. (actions.ts)

Versioned Configuration and Messaging:

• Extends the ActionsConstants.__TEMPORARY__DISALLOWED_RULES object to include version-specific disallowed rules for the PRE_ISSUE_ACCESS_TOKEN_URL_PATH action type.
• Specifically, the "token_exchange", "device_code", "organization_switch", "jwt_bearer", "saml2_bearer" rules are now disallowed for version v1.

UI Changes:

• V1

• V2

Checklist

• e2e cypress tests locally verified. (for internal contributers)
• Manual test round performed and verified.
• UX/UI review done on the final implementation.
• Documentation provided. (Add links if there are any)
• Relevant backend changes deployed and verified
• Unit tests provided. (Add links if there are any)
• Integration tests provided. (Add links if there are any)

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

Developer Checklist (Mandatory)

• Complete the Developer Checklist in the related product-is issue to track any behavioral change or migration impact.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 805848e8-5253-4e09-aa7b-942c56485f09

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.05%. Comparing base (156aa08) to head (d825a9b).
⚠️ Report is 42 commits behind head on next.

Additional details and impacted files

@@           Coverage Diff           @@
##             next   #10150   +/-   ##
=======================================
  Coverage   56.05%   56.05%           
=======================================
  Files          42       42           
  Lines        1024     1024           
  Branches      254      231   -23     
=======================================
  Hits          574      574           
  Misses        450      450           

Flag	Coverage Δ
@wso2is/core	56.05% <ø> (ø)

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.