[Feat] Populate support form from search params

[esizer]

🤖 Resolves #12215

👋 Introduction

Uses search params to pre-populate the support form subject and description fields.

🧪 Testing

Tip

When adding search params, make sure they are encoded for URIs.

1. Build the app pnpm run dev:fresh
2. Navigate to /support
3. Confirm the form is empty
4. Add search params for subject (only "bug", "feedback" and "question" are supported values) and description
5. Confirm the form is populated
6. Confirm unsupported subject fields leads to an empty "I'm looking to..." field
7. Confirm unsafe input to the description param is sanitized (i.e <script>alert('unsafe');</script> does nothing)

📸 Screenshot

[vd1992]

Question, where are the URLs supposed to be coming from? Do we have to generate them or is someone providing them to a user?

[esizer]

Question, where are the URLs supposed to be coming from? Do we have to generate them or is someone providing them to a user?

I think it can be both but likely that the majority will be generated on the client.

[vd1992]

Question, where are the URLs supposed to be coming from? Do we have to generate them or is someone providing them to a user?

I think it can be both but likely that the majority will be generated on the client.

Okay, so there should be a separate ticket then to generate the URLs then? I was a bit confused as to whether the issue scope included generating the URLs too

[petertgiles]

Nice! Works great. Thanks for the test, too.

[petertgiles]

Question, where are the URLs supposed to be coming from? Do we have to generate them or is someone providing them to a user?

This issue is part of the new applicant dashboard milestone. You can see if reference to it here: #12164 . I think this part of the whole "if you've been screened out, reach out to us to chat about it" thing.