Use 'vscode.open' instead of the 'open'

[jdneo]

Just a small suggestion, but using 'opn' is fine also...

For now, when we want to open a URL in the browser, we leverage the 'opn' module.

Actually, this module can be replaced with the VS Code embedded command, for example:

export async function openUrl(url: string): Promise<void> {
    await vscode.commands.executeCommand("vscode.open", vscode.Uri.parse(url));
}

[jdneo]

@EricJizbaMSFT

[StephenWeatherford]

Huh...

[jdneo]

Guess this could be closed...

[bwateratmsft]

I'm going to reopen this; the use of open does not permit opening of URLs from in-browser Codespaces. See microsoft/vscode-docker#2944 and microsoft/vscode-docker#2943.

[bwateratmsft]

Modified the title slightly since we now use open instead of opn.

[bwateratmsft]

Related also to #867

[bwateratmsft]

Maybe blocked by microsoft/vscode#85930 but probably need @ejizba to take a look.

[bwateratmsft]

I think that using vscode.env.openExternal may also get used as part of port forwarding with remote sessions.

[ejizba]

I don't think we'll fully switch to openExternal until that bug is fixed, but we could maybe special-case codespace scenarios

[bwateratmsft]

Is it frequent that we run into the URL parsing issues? If not, would it be practical to special case those and let the general case be vscode.env.openExternal?

[bwateratmsft]

This is fixed now by #1401