feat: [UIE-10284] - IAM: session token refresh

[aaleksee-akamai]

Description 📝

This PR fixes an issue with the session token during refresh.

• For account_admin / account_viewer, we only need to send a request using the parent token
• For not account_admin / account_viewer users, we don’t know the euuid because it is retrieved from the account endpoint, which returns 403 Unauthorized. So we need to take an euuid from child test account, store it and then use it to refresh a session

Changes 🔄

List any change(s) relevant to the reviewer.

• Send a payload with a parent token
• Fix a routing issue for delegate users
• Add logic for getting a euuid

Scope 🚢

Upon production release, changes in this PR will be visible to:

• All customers
• Some customers (e.g. in Beta or Limited Availability)
• No customers / Not applicable

How to test 🧪

Prerequisites

(How to setup test environment)

• use legacy parent account
• use account_admin parent account
• use not account_admin parent account

Reproduction steps

(How to reproduce the issue, if applicable)

• Login to CM as parent user and switch account to be delegate user.
• Wait for some time (around 10 mins). (You can modify timeRemaining.minutes to 13 in the SessionExpirationDialog component so you don’t have to wait)
• "Your session is about to expire" popup will appear.
• Click "Continue Working" button.

Verification steps

(How to verify changes)

• Session refresh works for all accounts

Author Checklists

As an Author, to speed up the review process, I considered 🤔

👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support

• I have read and considered all applicable items listed above.

As an Author, before moving this PR from Draft to Open, I confirmed ✅

• All tests and CI checks are passing
• TypeScript compilation succeeded without errors
• Code passes all linting rules