fix: [UIE-10308] - IAM Parent/Child - SwitchAccount Drawer: hide search if no child account

[abailly-akamai]

Description 📝

Small PR to hide the search bar in the SwitchAccountDrawer if there no child account to search for

Changes 🔄

List any change(s) relevant to the reviewer.

• Hide the search bar in the SwitchAccountDrawer if there no child account to search for

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 📷

Before	After

How to test 🧪

Prerequisites

An IAM parent/child account

Reproduction steps

Verification steps

• Ensure the current user isn't added to any delegation
• ✅ confirm the search fields is no longer displayed
• ✅ confirm no regression when added back to a child account delegation (esp while searching)
• ✅ confirm no regression with a legacy parent/child account

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]

Confirmed the verification steps. LGTM ✅

[bnussman-akamai]

Works as described!

From a UX perspective, is it a good or bad thing that we are eagerly hiding things?
As a user, I usually prefer to see the full experience (even if it is disabled) so that I know what the drawer will allow me to do in the future once I have access

For example:

[abailly-akamai]

@bnussman-akamai I raised this exact concern in the ticket - you can check the convo there. UX ruled in favor of the approach in this PR, which I also initially disagreed with. Not sure this is worth arguing a lot more over but including @tzmiivsk-akamai in this convo in case there's reconsideration after another concern is raised.

[tzmiivsk-akamai]

I’m still convinced that removing extra information here will reduce cognitive load and visual noise. For the empty state, we don’t need the search and the description.
However, @bnussman-akamai ’s example made me realize that it would be more appropriate to use the empty state from ADS here (I'm attaching a screenshot and the Figma link).
Additionally, I’ve added a Cancel button, as it was somehow missing from this drawer.

[bnussman-akamai]

That sounds good to me. Thanks @abailly-akamai & @tzmiivsk-akamai

[linode-gh-bot]

Cloud Manager UI test results

🔺 3 failing tests on test run #5 ↗︎

❌ Failing	✅ Passing	↪️ Skipped	🕐 Duration
3 Failing	869 Passing	11 Skipped	38m 5s

Details

Failing Tests
	Spec	Test
❌	object-storage.e2e.spec.ts	Cloud Manager Cypress Tests→object storage end-to-end tests » can create and delete object storage buckets
❌	account-switching.spec.ts	Cloud Manager Cypress Tests→Parent/Child account switching→From Child to Parent » can switch from Proxy user back to Parent account user from Billing page
❌	account-switching.spec.ts	Cloud Manager Cypress Tests→Parent/Child account switching→From Child to Child » can switch to another Child account as a Proxy user

Troubleshooting

Use this command to re-run the failing tests:

pnpm cy:run -s "cypress/e2e/core/objectStorage/object-storage.e2e.spec.ts,cypress/e2e/core/parentChild/account-switching.spec.ts"