fix: [UIE-10490, UIE-10564] - Mock relevant flags in alerts-related tests

[pmakode-akamai]

Description 📝

This PR fixes inconsistencies in Cypress alert-related tests caused by missing feature flag mocks.

Previously, tests were only relying on aclpServices (linode -> beta/new) flags. While this was somehow passing in CI, it fails locally because aclpAlerting / aclp (beta/new) flags were not mocked, leading to inconsistent and buggy behavior.

This PR adds the required flag mocks and cleans up test related constants for better clarity.

Related PRs:

• upcoming: [UIE-10490] - Configure New Feature Chip and Banner Messaging for Linode Alerts and Metrics #13509
• test: [UIE-10564] - Fix Linode Create alerts-create.spec.ts test failures #13527

Changes 🔄

• Added missing mocks for: aclpAlerting and aclp (beta/new) (Kept aclpServices flags as is to support contextual view)
• Renamed tests constants for clearer distinction between:
  • legacy vs ACLP modes and beta vs new phases
• Updated alerts-create tests to use the correct constants based on mocked flags

Scope 🚢

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

Target release date 🗓️

March End

Preview 📷

Before (dev branch In Local)	After (this branch)
	Test should pass locally as well as in CI ✅

How to test 🧪

Reproduction steps

• Run alerts-create.spec.ts locally and observe test failures.

Verification steps

• Run Cypress tests locally and Confirm all alert-related tests (especially alerts-create) pass
• Run unit tests for AclpPreferenceToggle.test.tsx and confirm all tests pass
• Verify behavior is consistent in both local and CI runs

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

[jdamore-linode]

Thanks @pmakode-akamai 👍 these were passing in CI because the test runs use the LaunchDarkly {{development}} environment, where the values were set differently than (presumably) the environment you're developing against locally.

(I also kicked off another test run: I flipped the Private Image Sharing feature flag yesterday for testing and forgot to change it back which triggered all these failures. Sorry about that!)

[linode-gh-bot]

Cloud Manager UI test results

🔺 2 failing tests on test run #7 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
2 Failing	886 Passing	11 Skipped	45m 11s

Details

Failing Tests
	Spec	Test
❌	access-key.e2e.spec.ts	Cloud Manager Cypress Tests→object storage access key end-to-end tests » can create an access key with limited access - e2e
❌	object-storage-objects-multicluster.spec.ts	Cloud Manager Cypress Tests→Object Storage Multicluster objects » can upload, access, and delete objects

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/objectStorage/access-key.e2e.spec.ts,cypress/e2e/core/objectStorageMulticluster/object-storage-objects-multicluster.spec.ts"