fix: General Service URI text in Database Summary page

[hana-akamai]

Description 📝

• Add <username>: to the general Service URI in the Database Summary page
• Display ssl-mode=REQUIRED for mysql clusters
• Display placeholder text while hosts are still being retrieved

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

3/31

Preview 📷

Before	After

How to test 🧪

Prerequisites

(How to setup test environment)

• Ensure you have the Database PgBouncer and HostnameEndpoints feature flag on
• Have a Postgres and Mysql Database

Reproduction steps

(How to reproduce the issue, if applicable)

• On remote devcloud, go to a Postgres' Database Cluster's summary page
• Click reveal password for the service URI under Connection Details
• The password does not include <username>:
• Go to a Mysql cluster's summary page
• The service URI ssl mode is sslmode=require instead of ssl-mode=REQUIRED
• Add a VPC with public access
• The Private Service URI hosts field displays undefined while hosts are being retrieved

Verification steps

(How to verify changes)

• Checkout this PR and point to devcloud locally
• Go to a Database Cluster's summary page and click reveal password for the service URI under Connection Details
• The password includes <username>:
• There should be no regressions with PgBouncer
• Go to a mysql cluster's summary page
• The service URI ssl mode is ssl-mode=REQUIRED
• Add a VPC with public access
• The Private Service URI hosts field displays a placeholder text while hosts are being retrieved

pnpm test ServiceURI

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

[smans-akamai]

Went through the verification steps and tested the changes locally. The updates look good!

[smans-akamai]

Using the steps to test adding a VPC with public access, I was able reproduce the bug and tested the verification steps for the fix. I can see the placeholder appearing, so this fix looks good!