fix: [UIE-10522] - Disable credential buttons for resuming state

[hana-akamai]

Description 📝

Disable buttons to get credentials when the Database cluster is resuming

Changes 🔄

• Add resuming to disabled states
• Add disabledReason prop to CopyTooltip
• Disable copy icon button in the Service URI field

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

Next release

Preview 📷

Before	After

How to test 🧪

Prerequisites

• Ensure you have Database PgBouncer and Hostname Endpoints feature flags on
• Checkout this PR and point to devcloud locally
• Have a Postgres Database cluster with at least one connection pool (add via Networking tab)

pnpm test CopyTooltip
pnpm test ServiceURI

Verification steps

(How to verify changes)

• Suspend the Postgres Database Cluster and navigate back to the suspended cluster's summary page
• The copy icon button should be disabled with tooltip explanation
• Resume the suspended cluster (via landing table) and navigate back to the cluster's summary page
• The Show password, {click to reveal password}, and copy icon buttons should be disabled

[smans-akamai]

We had a similar change before in #13487 where failed, provisioning, and suspended statuses would throw this error for credentials. Have we confirmed that this the full list of statuses that can cause this with the backend?

We may want to check to make sure there aren't any others that can cause this such as degraded, migrating, resizing, suspending, restoring.

[hana-akamai]

It looks like the backend throws an error for anything that isn't active, but it may become more permissive in the future. For example, Aiven does support reading the password for powered-off services such as suspending/suspended/resuming.

Removed failed since it's apparently no longer used by DBaaS and added suspending to the list.

The other states are very ephemeral (I wasn't able to catch the in-between resizing/restoring state), so I don't think it's a huge issue if the button isn't disabled. I think being too restrictive on the disabled state would introduce more potential issues (such as not being able to reveal if the API eventually matches Aiven's more permissive states) than the minor friction of an error

[smans-akamai]

I saw the discussion and it sounds like this could also change in the future. The different statuses you have listed for DISABLE_CREDENTIAL_STATES look good to me and we can also adjust it if we need to. This change looks good to me, thanks for looking into it!

[smans-akamai]

Went through the verification steps and ran the unit tests. Also checked the UI and the console errors/warnings were resolved. This looks good to me!

[smans-akamai]

I saw the discussion and it sounds like this could also change in the future. The different statuses you have listed for DISABLE_CREDENTIAL_STATES look good to me and we can also adjust it if we need to. This change looks good to me, thanks for looking into it!