Provide an easy way to add additional module paths to PSModulePath via settings

Some projects might benefit from an easy way to add paths to their PowerShell session's PSModulePath so that modules in non-standard paths are available for IntelliSense and parse-time checks.

One specific use case is developing multiple DSC resources in the same folder structure. You will get parse-time errors about missing DSC resources if your the other resources you're developing cannot be found in the PSModulePath.

It's fairly easy to change your Microsoft.VSCode_profile.ps1 to add your workspace path to $env:PSModulePath but that setting will not transfer to other developers in the project. If this was a workspace-level setting, it could be enabled for anyone who opens the code in VS Code.

Non vengono indicati file, test o punti di ingresso. Inizia chiarendo in che modo un'impostazione a livello di workspace dovrebbe aggiungere percorsi al PSModulePath della sessione PowerShell, incluse più risorse DSC; il lavoro è completato quando gli altri sviluppatori che aprono il workspace ricevono quei moduli per IntelliSense e i controlli in fase di parsing.