Clean up the dependency structure around the environment service

[inspirer]

This PR fixes #102918

I followed the example of INativeWorkbenchEnvironmentService and extracted IBrowserWorkbenchEnvironmentService, splitting the workspace configuration options into two files: vs/workbench/{common,browser}/options.ts. Maybe I should have used the 'Web' infix instead of 'Browser' to highlight that those are web-only components, not reusable in the electron version. I'm happy to follow up and update this pull request as needed.

This PR also adds missing code-import-patterns for the web version.

Now looking at the code one again, I wonder if we should promote all common contributions relying on the common environment service's options to browser as they don't make much sense in other environments. This can be done in a separate step though. There are:

• two under https://github.com/microsoft/vscode/tree/master/src/vs/workbench/contrib/remote/common
• webExtensionManagementService.ts initialized behind an if:

  vscode/src/vs/workbench/services/extensionManagement/common/extensionManagementServerService.ts

  Line 41 in 4ecf61e

  if (isWeb) {

[ghost]

All CLA requirements met.

[bpasero]

@inspirer are the code layer rules in ESLint something to extract from this PR if they make sense individually?

As for the rest, #102918 (comment) applies.

[inspirer]

Shall I extract the eslintrc change into a separate PR? I'll have to leave out the line that forbids common/environmentService.ts to depend on workbench.web.api.ts.

[bpasero]

Sorry but I am going ahead to close this, I feel I need to think about this problem myself and would not accept help in form of a PR.