upcoming: [UIE-10490] - Configure New Feature Chip and Banner Messaging for Linode Alerts and Metrics

[pmakode-akamai]

Description 📝

Configure New Feature Chip and Banner Messaging for Linode Alerts and Metrics

Changes 🔄

• Removed "Beta" from variable and prop names and replaced with more accurate terminology since modes are now legacy or ACLP. (ACLP can internally be in Beta, LA, or GA)
• Added getFeatureChip utility to the shared package
• Configured "New Feature" / "Beta" chips to rely on global flags: aclpAlerting (for Alerts) and aclp (for Metrics)

  instead of service-specific flags (aclpServices -> linode -> alerts/metrics -> beta)
• Added banner messaging for the post-beta (LA/GA) phase
• Added and updated unit test cases

Scope 🚢

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

Target release date 🗓️

End of March

Preview 📷

Context	Preview
For Alerts	Create Linode Flow -> Additonal Options: Linode Details -> Alerts tab:
For Metrics	Linode Details -> Metrics tab:

How to test 🧪

Prerequisites

• Use the following global flags to control banner messaging and New Feature chips:
  • aclpAlerting (for Alerts) - This is visible as CloudPulse Alerting in devtools
  • aclp (for Metrics) - This is visible as CloudPulse in devtools
    
• Enable contextual view via
  aclpServices -> linode -> alerts/metrics -> enabled
• Add the customer tag to your account in DevCloud Admin as specified in the ticket/epic

Verification steps

• Alerts
  • Create Linode -> Additional Options
    • Verify banner displays correctly in both legacy and ACLP modes
    • In ACLP mode:
      • Toggle Beta/New in devtools and verify the correct chip appears next to the "Alerts" heading
      • When Beta is ON -> show Beta banner
      • When Beta is OFF -> fallback to New banner (regardless of New flag state)
  • Linode Details -> Alerts tab (unified legacy + ACLP Alerts view)
    • Verify banner for Beta and New phases (aclpAlerting -> beta/new)
    • Ensure no banner when both Beta and New are OFF
    • Verify feature chip appears when either Beta or New is ON
• Metrics
  • Linode Details -> Metrics tab
    • Verify banner in legacy, Beta, and New phases (aclp -> beta/new)
    • When Beta is ON -> show Beta banner
    • When Beta is OFF -> fallback to New banner (regardless of New flag state)
    • Verify feature chip:
      • Shows when Beta or New is ON
      • Does not show when both are OFF
• Ensure no UI or labeling issues in any mode
• Ensure all tests pass

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