[Getting Started] Provide when clauses for workspace tags

[digitarald]

To make walkthroughs more contextual to the currently open project, they should to be aware what kind of files/packages are in the project.

One of the best (there might be others) existing signals VS Code offers are workspace tags. If they would be available in when clause context, walkthroughs (and other UI elements) could adapt to that to show additional extensions, settings or specialized features.

cc @jureid @JacksonKearl

[digitarald]

Via @chrisdias: Workspace tagging happens in LifecyclePhase.Eventually, so the information would only be available after some delay. The other risk is that it would be adding a dependency workspace tags, making later changes harder.

The way config/file extension recommendations work, using file patterns, could be more generic.

[JacksonKearl]

Discussed w/ @kieferrm, considering modifying this to instead give priority to walkthroughs based on files present in workspace. So a TS walkthrough might be top-of-list when ./tsconfig.json exists, and a Java walkthrough is top-of-list when ./Ant.xml exists.

[digitarald]

considering modifying this to instead give priority to walkthroughs based on files present in workspace.

For many cases we would duplicate the signals that extensions use to get activated. This could also the existing signal for when a language extension activated because of files in a workspace – combining the workspaceContains and onLanguage activationEvents. Or are there cases when these activation reason could be misleading?