Fixed devtools url used for debug with chrome and edge

[Dona278]

This PR ensure the correct creation of the devtools url with proxy to use for debug with chrome and edge browser which recently changed how urls are returned from "localhost:9222/json".

Browser tested:
Edge Version 136.0.3240.50
Chrome Version 136.0.7103.49

Fixes #61559

[thaystg]

I'm comfortable on approving the PR with the suggestions that @ilonatommy did, and also @ilonatommy if you have time can you give a double test? Maybe with an old and a new chrome/edge version?
Please let me know, if you don't have time to do it I'll try.

[javiercn]

@thaystg I'm not an expert in this area, so if you think the change is good enough, I'm happy with it.

Do you know if this affects debugging under VS or is this just for debugging directly from the dev tools?

[Dona278]

If can help: with that change, VS debug still works, and because all stuffs are under "display browser debug information" context and are based only on what browser returns back if lanched with specific command, I think that VS debugging isn't affected.
Meanwhile I will update the code to reflect your the suggestions.

[Dona278]

@thaystg after applied suggestions I saw that the code can be changed to a simple "if it is already correct use as is, othewise keep its query string and append to the default browser devtools path". I also added comment which explain that with example of new (both chrome and edge) and old version. @javiercn now I think it is more clear the reason why.

[javiercn]

Thanks for the changes, it's much simpler and clearer now. I only have one remaining piece of feedback about using UriHelper.FromAbsolute instead of manually processing the URL as that is "safer" and more future proof.

[thaystg]

@thaystg I'm not an expert in this area, so if you think the change is good enough, I'm happy with it.

Do you know if this affects debugging under VS or is this just for debugging directly from the dev tools?

This does not affect VS debugger.

[javiercn]

Thanks for the contribution!

[Dona278]

Will be also backported to next net9 release?

[ilonatommy]

@thaystg, I'm catching up after the holidays, I don't think I can test it any soon. CI failures are not connected.

[javiercn]

@Dona278 thanks for the contribution!

@ilonatommy let's get this into preview5 and we can see about backporting it later. I've just triggered the PR so that it's ready should we want to do it.

[javiercn]

/backport to release/9.0

[github-actions]

Started backporting to release/9.0: https://github.com/dotnet/aspnetcore/actions/runs/15042046220