Support configuration contribution points of resolver extensions

[connor4312]

1. Register some configuration defaults like { hello: "world" } using the web API (e.g. here for the code-server.sh script)
2. 🐛 notice they are still undefined when read from the local extension host (at least before a remote is resolved)

It seems like it should work because the overrides are registered here

vscode/src/vs/workbench/services/configuration/browser/configuration.ts

Lines 48 to 50 in 25dd3cf

	if (environmentService.options?.configurationDefaults) {
	this.configurationRegistry.registerDefaultConfigurations([{ overrides: environmentService.options.configurationDefaults }]);
	}

before the MainThreadConfiguration is even instantiated, so I would expect they get passed during initial hydration here

vscode/src/vs/workbench/api/browser/mainThreadConfiguration.ts

Line 29 in 25dd3cf

proxy.$initializeConfiguration(this._getConfigurationData());

...but they do not. I did some debugging myself but got a bit lost in config land.

Having these options is needed for a couple partner team feature asks.

[sandy081]

Assigning to August for investigation.

[sandy081]

I changed the default of workbench.colorTheme setting and it works (github.dev also uses the same). You should have the setting registered for the default to be applied. I suspect the setting is not registered in your scenario?

[connor4312]

The setting is registered. Repro is a little annoying since it requires an extension doing the resolution of the remote.

1. Run vscode.dev locally so that you can debug things (npm install && npm run build && node out/server/main.js)
2. Clone https://github.com/microsoft/vscode-remote-tunnels. git checkout connor4312/preference-auth-provider && npm install && npm run watch in one terminal, and cd extension && npx serve -p 3001 --cors in another
3. With devtools open, go to http://localhost:3000/+aHR0cDovL2xvY2FsaG9zdDozMDAx/some-tunnel-here (first segment is base64-encoded localhost:3001; the tunnel does not actually need to be hosted.) You can add ?vscode-quality=dev to that URL to use your local vscode build found in a sibling folder to vscode-dev.
4. Notice that even though we set a default value for remote.tunnels.useAuthProvider, it's undefined when you hit the debugger statement.

[sandy081]

Thanks for the steps. I can confirm that the setting is not yet registered at the time when you are accessing this setting in your extension. Your extension (remote resolver) is accessing this setting while resolving the authority and I suspect, contribution points of this extension are not read/handled yet.

@alexdima Can you please confirm if this is true.