[release/8.0-preview5] [wasm][debugger] Remove usage of GeneratedRegex

[github-actions]

Backport of #86911 to release/8.0-preview5

/cc @thaystg

The P5 BrowserDebugHost is compiled as part of the runtime build but consumed in aspnetcore at a transport package and previously used the RegexSourceGenerator. Because dotnet/runtime builds with the SDK set by arcade in global.json when BrowserDebugHost was compiled with the Preview4 SDK the and regex source generator used IndexOfAnyValues which no longer exists in the P5 runtime after dotnet/docs#35244 so the proxy fails to bind breakpoints using a P5 runtime.

This stops using the source generator for to regex code to avoid the missing symbol.

Customer Impact

Blazor wasm debugging fails in preview5.

Testing

Manual

Risk

Low, the problem is confined to the debug proxy which does not work at all without this change.

[ghost]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Backport of #86911 to release/8.0-preview5

/cc @thaystg

Customer Impact

Testing

Risk

IMPORTANT: If this backport is for a servicing release, please verify that:

• The PR target branch is release/X.0-staging, not release/X.0.

• If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.

Author:	github-actions[bot]
Assignees:	-
Labels:	area-Debugger-mono
Milestone:	-

[lewing]

The debugger is only tested in runtime so if this is approved you can fast track downstream builds

[carlossanlop]

@lewing @radical ping me when this is ready to merge.

[lewing]

@carlossanlop It is safe to merge, the linux lane passed and there is nothing windows specific about the change

[thaystg]

@carlossanlop it's ready to be merged. No reasons to wait until windows lane finishes.