chore(admin): deeplink to RP when creating WAF bypass token

[toufali]

Because

• Admins clicking "manage in WAF Bypass Tokens" from a relying party with no token lost all RP context and had to manually find and reselect the RP in the create form.

This pull request

• Updates the RP panel link to carry createForClientId and name query params so the WAF bypass form is prefilled with RP context.

Issue that this pull request solves

Closes: FXA-13769

Checklist

Put an x in the boxes that apply

• My commit is GPG signed.
• If applicable, I have modified or added tests which pass locally.
• I have added necessary documentation (if appropriate).
• I have verified that my changes render correctly in RTL (if appropriate).
• I have manually reviewed all AI generated code.

To test

1. visit relying parties page in admin panel
2. choose an RP (or create one) -- notice the last row has a link to attach a WAF Bypass token
3. click the WAF bypass token link

Expected results with change: you are navigated to the WAF bypass token panel, and the "generate token" flow is active with the RP details pre-populated.

Expected results without change: you are navigated to the WAF bypass token panel.

[Copilot]

Pull request overview

This PR improves the FxA Admin Panel workflow for creating WAF bypass tokens by preserving relying party (RP) context when navigating from an RP detail view to the WAF Tokens page, using query params to prefill the create-token form.

Changes:

• Add support in the WAF Tokens page to consume createForClientId and name query params, auto-open the create form, and then clear those params from the URL.
• Add unit tests covering auto-open/prefill behavior and query param clearing.
• Update the Relying Parties page to deeplink to the WAF Tokens page with the appropriate prefill query params.

Reviewed changes

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

File	Description
packages/fxa-admin-panel/src/components/PageWafTokens/index.tsx	Consume query params to prefill/auto-open the create token form and clear params from the URL.
packages/fxa-admin-panel/src/components/PageWafTokens/index.test.tsx	Add tests validating prefill/auto-open behavior and query param cleanup.
packages/fxa-admin-panel/src/components/PageRelyingParties/index.tsx	Update RP panel link to deeplink into token creation with RP context.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[LZoog]

I see it working locally, so r+!

[LZoog]

Not sure off the top of my head why id can be undefined when I see MOCK_RP_A set with an id and I see id: string; on RelyingPartyDto 🤔

[toufali]

Good Q — these fixtures are typed Partial<RelyingPartyDto> (to avoid filling in the ~10 fields the test doesn't read), which makes every property optional. So even though the literal sets id, TS widens MOCK_RP_A.id to string | undefined and needs the !...

[LZoog]

The alternative here was just to use the router state like <NavLink to="/waf-tokens" state={{ clientId, name }}> and then read it on the other page. It would persist across a refresh too and we wouldn't have to delete the params after reading them on the next page. Usually we use query params for some external state but I think this is OK too if you prefer it as the work has already been done - if we ever want to send this as a link, this will work better🤷‍♀️