upcoming: [M3-7580] - Add list view for Linode Clone/Backup

[hkhalil-akamai]

Description 📝

Introduces a list view for selecting linodes to clone/restore from in the create UI.

This is the final PR of the Linode Clone UI Updates.

Changes 🔄

• Introduces a new list view for large-screen (mdUp) devices
• List view displays Linode label, status, image, plan and region
• Includes inline "Power Off" action button for running linodes.

Preview 📷

Before	After
Clone Linode
Backups

How to test 🧪

Prerequisites

• Ensure "Linode Clone UI Changes" feature flag is turned on

Verification steps

• Enter the Linode Create flow, either through the "Create" menu on the top-left corner of the app or by selecting "Clone" in the action menu for a linode
• In both the "Clone Linode" and "Backups" tabs:
  • Linode label, status, image, plan and region are displayed
  • Sorting works as expected for all fields
  • For running Linodes: Power Off button is displayed and clicking it displays a confirmation dialog
  • For small displays, list reverts back to the original cards view
• In the "Clone Linode" tab only:
  • Selecting a linode populates the region, plan selection and label fields
• In the "Backups" tab only:
  • Selecting a linode displays all available backups for that linode

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
• [x] 👣 Providing comprehensive reproduction steps
• [x] 📑 Providing or updating our documentation
• [x] 🕛 Scheduling a pair reviewing session
• [x] 📱 Providing mobile support
• [x] ♿ Providing accessibility support

[abailly-akamai]

@hkhalil-akamai you also need to trigger the code coverage and e2e suite with another commit. I wonder if the e2e suite is going to trip or keep testing the old UI (if it is covered at all, which I think it is) - either way you will need to mock the flag to test the new UI

[hkhalil-akamai]

@hkhalil-akamai you also need to trigger the code coverage and e2e suite with another commit. I wonder if the e2e suite is going to trip or keep testing the old UI (if it is covered at all, which I think it is) - either way you will need to mock the flag to test the new UI

Ooh I didn't think about this, does the test environment use development flags? (I believe the flag is enabled in dev).

[abailly-akamai]

@hkhalil-akamai

does the test environment use development flags

you can mock those. ex: https://github.com/linode/manager/blob/develop/packages/manager/cypress/e2e/core/account/account-login-history.spec.ts#L44-L48

You can mock the flag off for now so it passes for this PR, but you need a follow up ticket to handle the new flow before the flag is turned on in any environment (if you get failures)

[github-actions[bot]]

Coverage Report: ✅
Base Coverage: 81.32%
Current Coverage: 81.34%

[hkhalil-akamai]

Changed notices to use bullet points as suggested by @abailly-akamai:

Before	After
Clone Linode
Backups

[hkhalil-akamai]

Verified all E2E tests pass locally with feature flag enabled.