Avoid querying the Python extension for the interpreter

[dhruvmanila]

Summary

Fix the CI failure on main. I think the tests are currently unpredictable in the sense that the tests could begin before the server starts which then creates the failure. The main reason I believe this is happening is because the extension uses a PubSub mechanism here:

ruff-vscode/src/common/python.ts

Lines 250 to 259 in 80d1b13

	if (api) {
	disposables.push(
	api.environments.onDidChangeActiveEnvironmentPath((e) => {
	onDidChangePythonInterpreterEvent.fire({ path: [e.path], resource: e.resource?.uri });
	}),
	);
	traceLog("Waiting for interpreter from python extension.");
	onDidChangePythonInterpreterEvent.fire(await getInterpreterDetails());
	}

This change is so that it never hits this by always testing with the bundled executable and always using the native server.

Test Plan

I don't really have a good way to test this until it's being triggered multiple times which will verify the consistency now.