feat: [UIE-10778] - IAM LA/New flag fix

[mpolotsk-akamai]

Description 📝

This PR removes the "Limited Availability" badge since IAM is now fully rolled out to all users.
A new flag has been introduced to control the visibility of the "NEW" badge independently. All logic related to iamLimitedAvailabilityBadges has been removed.

Changes 🔄

List any change(s) relevant to the reviewer.

• Removed the "Limited Availability" badge
• Add a new flag to control the display of the "NEW" badge
• Removed iamLimitedAvailabilityBadges flag and all related logic

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

Preview 📷

Include a screenshot <img src="" /> or video <video src="" /> of the change.

🔒 Use the Mask Sensitive Data setting for security.

💡 For changes requiring multiple steps to validate, prefer a video for clarity.

Before	After

How to test 🧪

Prerequisites

(How to setup test environment)

• use IAM Parent/Child account

Verification steps

(How to verify changes)

• Verify that the "Limited Availability" badge is no longer displayed anywhere in IAM
• Verify that the "NEW" badge is displayed only when the new flag is enabled
• Disable the new "NEW" flag and confirm the badge is not shown

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

[linode-gh-bot]

Cloud Manager UI test results

🔺 14 failing tests on test run #1 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
14 Failing	888 Passing	11 Skipped	67m 11s

Details

Failing Tests
	Spec	Test
❌	create-linode-from-image.spec.ts	Cloud Manager Cypress Tests→create linode from image, mocked data » creates linode from image on images tab
❌	rebuild-linode.spec.ts	Cloud Manager Cypress Tests→rebuild linode » rebuilds a linode from Image
❌	rebuild-linode.spec.ts	Cloud Manager Cypress Tests→rebuild linode » rebuilds a linode from Community StackScript
❌	rebuild-linode.spec.ts	Cloud Manager Cypress Tests→rebuild linode » rebuilds a linode from Account StackScript
❌	rebuild-linode.spec.ts	Cloud Manager Cypress Tests→rebuild linode » cannot rebuild a provisioning linode
❌	rebuild-linode.spec.ts	Cloud Manager Cypress Tests→rebuild linode » can rebuild a Linode reusing existing user data
❌	rebuild-linode.spec.ts	Cloud Manager Cypress Tests→rebuild linode » can rebuild a linode with the GECKO is enabled
❌	create-image.spec.ts	Cloud Manager Cypress Tests→create image (e2e) » create image from a linode
❌	smoke-create-image.spec.ts	Cloud Manager Cypress Tests→create image (using mocks) » create image from a linode
❌	images-non-empty-landing-page.spec.ts	Cloud Manager Cypress Tests→image landing checks for non-empty state with restricted user » checks restricted user with read access has no access to create image and can see existing images
❌	object-storage.e2e.spec.ts	Cloud Manager Cypress Tests→object storage end-to-end tests » can update bucket access
❌	restricted-user-details-pages.spec.ts	Cloud Manager Cypress Tests→restricted user details pages » should disable action elements and buttons in the 'Images' details page
❌	images-empty-landing-page.spec.ts	Cloud Manager Cypress Tests→Images empty landing page » shows the empty state when there are no images
❌	images-empty-landing-page.spec.ts	Cloud Manager Cypress Tests→Images empty landing page » checks restricted user has no access to create Image on Image landing page

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/images/create-linode-from-image.spec.ts,cypress/e2e/core/linodes/rebuild-linode.spec.ts,cypress/e2e/core/images/create-image.spec.ts,cypress/e2e/core/images/smoke-create-image.spec.ts,cypress/e2e/core/images/images-non-empty-landing-page.spec.ts,cypress/e2e/core/objectStorage/object-storage.e2e.spec.ts,cypress/e2e/core/account/restricted-user-details-pages.spec.ts,cypress/e2e/core/images/images-empty-landing-page.spec.ts"