fix: [DI-29172] - Dependent API error handling in Edit Alert

[santoshp210-akamai]

Description 📝

This PR implements error handling for dependent API failures in the CloudPulse Edit Alert feature

Changes 🔄

-Added hasAPIError boolean field to track API errors across the alert form
-Implemented error detection in components that make API calls (notification channels, metric criteria, dimension filters)
-Display warning notice and disable submit button when API errors occur

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

Target release date 🗓️

Please specify a release date (and environment, if applicable) to guarantee timely review of this PR. If exact date is not known, please approximate and update it as needed.

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
edit-form-before.mp4	edit-form-after.mp4

How to test 🧪

Prerequisites

(How to setup test environment)

• Under Monitor, click on Alerts.
• Choose an Alert, click on the Action Menu and choose the Edit alert option
• In the form, try to disable any of the API's the form might use e.g.,(alert-channels, metric-definition, instances, endpoints, regions, )

Reproduction steps

(How to reproduce the issue, if applicable)

• Verify that the submit button is disabled and Notice component is there for any dependent API failures
• Verify that on a retry if api is successful, the submit button is enabled and Notice component is not there

Verification steps

(How to verify changes)

• Verify that for every

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

🎉 866 passing tests on test run #3 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
0 Failing	866 Passing	11 Skipped	37m 38s