upcoming: [UIE-9327] - Add service URIs to Database summary tab

[hana-akamai]

Description 📝

• Display general Service URI for all databases under Connection details in the summary tab
• If applicable, display PgBouncer connection details Service URI for postgres clusters with at least one connection pool

Changes 🔄

List any change(s) relevant to the reviewer.

• Refactor Database CA Certificate into a separate file
• Refactor Service URI to include general support
• Add general and PgBouncer service URIs to Database summary tab

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

Preview 📷

Mysql	Postgres

How to test 🧪

Prerequisites

(How to setup test environment)

• Ensure the Database PgBouncer feature flag is enabled and turn on the legacy MSW

Verification steps

(How to verify changes)

• Go to a mysql Database cluster's summary page and confirm that a general mysql service URI displays under Connection Details. There should not be a PgBouncer section.
• Go to a postgres Database cluster's summary page and confirm that a general postgres service URI displays under Connection Details. There should be a PgBouncer section

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

[mpolotsk-akamai]

Tested verification steps:

• MySQL Database Summary page shows the service URI under Connection Details.
• PostgreSQL Database Summary page shows the service URI under Connection Details and the PgBouncer section.

[linode-gh-bot]

Cloud Manager UI test results

🔺 1 failing test on test run #6 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
1 Failing	854 Passing	11 Skipped	44m 39s

Details

Failing Tests
	Spec	Test
❌	clone-linode.spec.ts	Cloud Manager Cypress Tests→clone linode » can clone a Linode from Linode details page

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/linodes/clone-linode.spec.ts"

[smans-akamai]

It may not be necessary, but I'm wondering if it would make sense to add some kind of error state for this field in the event that the connection-pools GET call fails. Currently it just hides the PgBouncer Connection Details field as a whole, but they won't actually see any error messaging until they navigate to the Networking tab.

[smans-akamai]

The changes look great and all my feedback has been addressed! I left a follow up comment on the error handling behavior in the summary tab, as something we might want to consider.

But this looks good to me so I've approved!