feat: [UIE-8002] - DBaaS 2.0 Landing Page

[mpolotsk-akamai]

Description 📝

DBaaS 2.0 Landing Page and Empty Landing Page

Changes 🔄

• Added Tabs to the Landing Page: Two tabs for Beta customers, labeled "Legacy Databases" and "New Databases."
• Added Logo(including dark theme): Displayed on the Empty Landing Page, in the "New Databases" tab, and in the "New Databases" single table view.
• Single Table Landing Page: Added for Beta customers without "Legacy Databases" but with "New Databases," and for new customers with only "New Databases."
• New "Plan" Column: Added to the "New Databases" table.
• Added Info Banner: Included on the landing page.

Target release date 🗓️

9/9/24

Preview 📷

Include a screenshot or screen recording of the change

:bulb: Use <video src="" /> tag when including recordings in table.

Before	After

How to test 🧪

Prerequisites

(How to setup test environment) Enable DatabaseV2Beta flag

Verification steps

(How to verify changes)

1. Navigate to the Databases section.
2. For new customers (with no legacy or new databases), the Landing Page will display an Empty Landing Page with a Logo.
3. For customers with Legacy Databases, the Landing Page will show tabs for "Legacy Databases" and "New Databases," along with an info banner.
4. When "New Databases" tab is selected, the page will display a table with an additional "Plan" column and a logo below the table. The "Configuration" column will be renamed to "Nodes." The table will be empty if no new databases are present.
5. For customers without Legacy Databases but with New Databases, the Landing Page will show a single table with a "Plan" column and the "Configuration" column renamed to "Nodes," an info banner, and a Logo below the table.
6. If the DatabaseV2Beta flag is disabled, the Landing Page will display a single table with no changes.

As an Author I have considered 🤔

Check all that apply

• [x] 👀 Doing a self review
• [x] ❔ Our contribution guidelines
• [x] 🤏 Splitting feature into small PRs
• [x] ➕ Adding a changeset
• [x] 🧪 Providing/Improving test coverage
• [x] 🔐 Removing all sensitive information from the code and PR description
• [x] 🚩 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

[mjac0bs]

@mpolotsk-akamai I just merged in #10786 so we'll want to rebase this PR on develop.

[mpolotsk-akamai]

@mpolotsk-akamai I just merged in #10786 so we'll want to rebase this PR on develop.

@mjac0bs , thanks, I've rebased the PR

[github-actions[bot]]

Coverage Report: ✅
Base Coverage: 86.63%
Current Coverage: 86.63%

[mjac0bs]

@mpolotsk-akamai Just noticed that typecheck is was failing - using the optional chaining operator to access databases?.data should fix that where there are errors.

[mpolotsk-akamai]

Just want to call out the failing Cypress tests in create-database.spec.ts so we don't accidentally merge this before they're fixed.

It looks like the tests are failing because no regions are appearing in the region select drop-down -- that's probably caused by something not being mocked

@jdamore-linode, I've fixed the issue.

[jdamore-linode]

Nice! Thanks @mpolotsk-akamai!