feat(FR-2183): rename MyKeypairInfoModal to legacy and add @since branching

[agatha197]

Resolves #6092(FR-2183)

Changes

• Rename MyKeypairInfoModal.tsx to MyKeypairInfoModalLegacy.tsx with TODO comment for removal after 27.4.0
• Add placeholder MyKeypairManagementModal.tsx for backend >= 26.4.0
• In UserSettingsPage.tsx, use baiClient.isManagerVersionCompatibleWith('26.4.0') to conditionally render the new management modal or the legacy modal

Verification

bash scripts/verify.sh → === ALL PASS ===

Checklist: (if applicable)

• Documentation
• Minimum required manager version (26.4.0 for new modal)
• Specific setting for review
• Minimum requirements to check during review
• Test case(s) to demonstrate the difference of before/after

[agatha197]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat(FR-2183): add set as main and deactivate actions for active tab #6103 : 2 dependent PRs (#6106 , #6108 )
• feat(FR-2183): add issue new keypair mutation and credential result modal #6102
• feat(FR-2183): create MyKeypairManagementModal with myKeypairs query, tabs, and table #6100
• feat(FR-2183): rename MyKeypairInfoModal to legacy and add @since branching #6099 👈 (View in Graphite)
• feat(FR-2183): add keypair self-service management feature spec #6019
• main

---

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• flow:merge-queue - adds this PR to the back of the merge queue
• flow:hotfix - for urgent changes, fast-track this PR to the front of the merge queue

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has required the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Coverage report for ./react

St.❔	Category	Percentage	Covered / Total
🔴	Statements	8.81% (-0% 🔻)	1543/17517
🔴	Branches	7.58% (-0% 🔻)	930/12268
🔴	Functions	5.7% (-0% 🔻)	278/4881
🔴	Lines	8.48% (-0% 🔻)	1446/17048

Show new covered files 🐣

St.❔	File	Statements	Branches	Functions	Lines
🔴	... / MyKeypairManagementModal.tsx	0%	100%	0%	0%
🔴	... / MyKeypairInfoModalLegacy.tsx	0%	0%	0%	0%

Test suite run success

784 tests passing in 37 suites.

Report generated by 🧪jest coverage report action from 02dd7f0

[Copilot]

Pull request overview

This PR introduces manager-version branching for the “My keypair info” modal in the user settings page by keeping the existing implementation as a legacy modal and routing newer managers to a new (future) management modal.

Changes:

• Renamed the existing keypair info modal into a legacy component and updated the Relay query name accordingly.
• Added a new MyKeypairManagementModal component and switched UserSettingsPage to conditionally render legacy vs. new modal based on manager version compatibility.
• Added useSuspendedBackendaiClient() usage in UserSettingsPage to drive the version gate.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
react/src/pages/UserSettingsPage.tsx	Adds manager-version gate to choose between legacy info modal and new management modal.
react/src/components/MyKeypairManagementModal.tsx	Introduces a new (currently placeholder) modal for keypair management on newer managers.
react/src/components/MyKeypairInfoModalLegacy.tsx	Renames the old modal + Relay query type/name to “Legacy” for backward compatibility.

[nowgnuesLee]

LGTM

[ironAiken2]

LGTM