feat: add configuration for workspace trust

[atscott]

Our extension does not support untrusted workspaces because it executes
ngcc from node_modules.

See microsoft/vscode#120251 for a description
of workspace trust and how to determine if an extension should support
untrusted workspaces.

Fixes #1322

[kyliau]

According to microsoft/vscode#120251 (comment) if supported is false, then we should also add a description field to explain why.

[TylerLeonhardt]

Do you always pull ngcc from the node_modules in the workspace? If there is any fallback behavior of loading ngcc from the node_modules that ship in your extension, you could theoretically support the limited case.

I bring this up because it would be nice to have Go To Definition support for untrusted workspaces so folks can at least navigate with ease.

[atscott]

@TylerLeonhardt We don't have a fallback for ngcc and it needs to run so that the Ivy compiler has metadata for the Angular libraries. Two other things to consider:

• We won't need ngcc forever. With the release of ng-linker in v12, libraries are able to publish in an already Ivy-compatible way. There will be a point in the future when we can stop running ngcc completely but it'll be some time.
• getProbeLocations was previously used to resolve ngdk from the workspace but we removed support for this in fb0b900. We'll need to remove the section of code there that adds workspace locations to the probe paths.
• We could consider enabling the language service without running ngcc. This might be able to provide some amount of useful information in templates. I'll add this to our notes to discuss in our sync today.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}