fix: [UIE-10337] updated error message in marketplace contact sales drawer

[tvijay-akamai]

Description 📝

Updated rate limiting error message on UI in marketplace contact sales drawer

Changes 🔄

List any change(s) relevant to the reviewer.

• Updated rate limiting error message on UI in marketplace contact sales drawer

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 🗓️

March end

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

[pmakode-akamai]

I'm able to see the updated error message ✅

I wonder if the API could return a UI-friendly message directly instead of CM partially transforming it for display. Not sure if the current message is used elsewhere, but it might help simplify things.

Also, could we add a changeset for this fix?

[grevanak-akamai]

PR is good to merge after adding changeset.

[tvijay-akamai]

I'm able to see the updated error message ✅

I wonder if the API could return a UI-friendly message directly instead of CM partially transforming it for display. Not sure if the current message is used elsewhere, but it might help simplify things.

Also, could we add a changeset for this fix?

This was not changed in backend side since as per them It's usually better for API users to know the exact limits.
Also, this message sits in the APIV4 layer so any change here would need to happen in APIV4. They are trying avoid changes there as much as possible as their team is very rigid. So we agreed to change this on UI.