Use vscode builtin extensions v1.70.2

[marcdumais-work]

What it does

Some time between 1.66.2 and 1.70.2, the references-view extension "ms-vscode.references-view" has gone from a standalone extension, that has its own repository, to a vscode built-in extension, that's part of the vscode repository. With that change, the extension's publisher has been updated from "ms-vscode" to "vscode". As of 1.70.2, this extension is referenced in the builtins extension pack and no longer needs to be specifically referenced in package,json.

This PR contains the following:
Example application:

• update the builtin extension pack to v1.70.2
• remove entry for old references-view extension, add it to "theiaPluginsExcludeIds"
• remove pinning for typescript extensions.

typescript browser tests:

• use new publisher when referencing references-view builtin
• re-try sending "Escape" to close the peek widget if it remains opened

How to test

Note: This PR is expected to fail CI until the vscode builtins v1.70.2 are published to openvsx.org. Once that's done, we should be able to fetch the new builtin pack and the extensions it refers-to, including the recently renamed vscode.references-view extension, using yarn download:plugins.

To test:

• build the repo and example application
• verify that the new builtins seem to work ok (at least the important ones like typescript, ...)
• verify that CI passes

Review checklist

• As an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• As a reviewer, I agree to behave in accordance with the review guidelines

[vince-fugnitto]

LGTM 👍

I think we should wait till v1.70.2 is published else we will download both ms-vscode.references-view and vscode.references-view.

[ccorn]

The extension pack 1.70.2 bundles both ms-vscode.references-view and vscode.references-view.
Is that a bug?
If so, should ms-vscode.references-view be added to theiaPluginsExcludeIds?

[marcdumais-work]

The extension pack 1.70.2 bundles both ms-vscode.references-view and vscode.references-view. Is that a bug? If so, should ms-vscode.references-view be added to theiaPluginsExcludeIds?

Indeed - I accidentally forgot to update the script that creates the extension pack, when I published the builtins v1.70.2 (it will be for the next release). I am doing the change you suggest, as we speak.

[marcdumais-work]

LGTM +1

I think we should wait till v1.70.2 is published else we will download both ms-vscode.references-view and vscode.references-view.

@vince-fugnitto builtins 1.70.2 are published. I have added an entry in theiaPluginsExcludeIds to exclude the old name for the references extension, so that only the new version will be present.

[vince-fugnitto]

LGTM 👍
I no longer see the duplicate "find all references" functionality present in the example applications.