Secure URL

Environment (please complete the following information):

• OS (e.g., Windows 10): Windows 11
• Extension version (e.g., 1.2.3): 2.1.1

Describe the bug:

My project has a .Net Core 6.0 backend that launches an Angular 14 application, based on the "ASP.NET Core with Angular" template. I am unable to use the extension browser to navigate to the projects url, "https://localhost:44372/".

Repro steps:
When I start the project using the default launcher, the backend code runs and a new Edge browser is launched to "https://localhost:44372/" and I can use the app.
Then, when I start the Chrome extension in Visual Studio Code, the extension browser starts on its start page. After I paste "https://localhost:44372/" to replace the start page's file URL, the extension pre-pends it with "http", resulting in "http://https//localhost:44372/" and no navigation, rendering it utterly useless.

Expected behavior:

I should be able to navigate to "https://localhost:44372/"

Additional context:

Reproduce the issue in the extension browser by entering https://localhost:44372/ after starting the ASP.NET Core with Angular project. Trace the URL handling from the address entry point and verify that an HTTPS URL is preserved and navigation reaches the project instead of producing http://https//localhost:44372/.