[release/9.0] Fixed devtools url used for debug with chrome and edge

[github-actions]

Backport of #61813 to release/9.0

/cc @javiercn @Dona278

Fixed devtools url used for debug with chrome and edge

Summary of the changes (Less than 80 chars)

Description

{Detail}

Fixes #{bug number} (in this specific format)

Customer Impact

{Justification}

Regression?

• Yes
• No

[If yes, specify the version the behavior has regressed from]

Risk

• High
• Medium
• Low

[Justify the selection above]

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

---

When servicing release/2.1

• Make necessary changes in eng/PatchConfig.props

[dotnet-policy-service]

Hi @@github-actions[bot]. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document.
Otherwise, please add tell-mode label.

[dotnet-policy-service]

Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime.
To make sure no conflicting changes have occurred, please rerun validation before merging. You can do this by leaving an /azp run comment here (requires commit rights), or by simply closing and reopening.

[Dona278]

@javiercn courtesy ping hoping that will be merged before next net9 release 🙏

[javiercn]

@Dona278 I need to check if this is already in a public .NET 10.0 release.

We normally fix things first in a preview then backport the patch. It might take an extra patch cycle as that help us reduce risk. I have triggered the PR tests to make sure that it is ready when we decide to merge it, and I'll bring it up for consideration on the next patch cycle.

[javiercn]

@ilonatommy were you looking at these same E2E test failures recently?

[thaystg]

Will we backport to release/8.0?