Ignore cache when querying for interpreters during auto-selection

[kimadeline]

Closes #16727

Note: The check that we wanted to use to prevent auto-selection from running again (checking the workspace state using getWorkspaceState doesn't work.

vscode-python/src/client/common/configSettings.ts

Lines 679 to 689 in ae979b1

	const autoSelectedPythonInterpreter = this.interpreterAutoSelectionService.getAutoSelectedInterpreter(
	this.workspaceRoot,
	);
	if (autoSelectedPythonInterpreter) {
	this.pythonPath = autoSelectedPythonInterpreter.path;
	if (this.workspaceRoot) {
	this.interpreterAutoSelectionService
	.setWorkspaceInterpreter(this.workspaceRoot, autoSelectedPythonInterpreter)
	.ignoreErrors();
	}
	}

PythonSettings.update makes the earliest auto-selection related call, and it turns out that the return value on line 679 will be the global interpreter:

vscode-python/src/client/interpreter/autoSelection/index.ts

Lines 146 to 161 in ae979b1

	public getAutoSelectedInterpreter(resource: Resource): PythonEnvironment | undefined {
	// Do not execute anycode other than fetching fromm a property.
	// This method gets invoked from settings class, and this class in turn uses classes that relies on settings.
	// I.e. we can end up in a recursive loop.
	const workspaceState = this.getWorkspaceState(resource);
	if (workspaceState && workspaceState.value) {
	return workspaceState.value;
	}
	const workspaceFolderPath = this.getWorkspacePathKey(resource);
	if (this.autoSelectedInterpreterByWorkspace.has(workspaceFolderPath)) {
	return this.autoSelectedInterpreterByWorkspace.get(workspaceFolderPath);
	}
	return this.globallyPreferredInterpreter.value;
	}

So autoSelectedPythonInterpreter will always be set. We can revisit that once we release though (#16735).