Auto-selected local environment not reflected in the status bar

[kimadeline]

From #16723 (review):

When in the new sorting/auto-selection experiment (#16520):

1. The first time updateDisplay is called the interpreter is python, so it will trigger auto-selection, so far so good;
2. The new auto-selection logic will query interpreterService.getInterpreters, however this call will return cached interpreters, so the interpreter that will be displayed in the status bar is going to be one of my cached global interpreters;
3. Then the auto-selection will be triggered again, this time by ExtensionActivationManager.activate, and this time the local virtual environment selected will be returned, but there is no updateDisplay call to reflect that change.

Proposed solution from @karrtikr: Add a way for getInterpreters to return fresh workspace envs and cached global envs (instead of just cached global envs)

[karrtikr]

The new auto-selection logic will query interpreterService.getInterpreters, however this call will return cached interpreters

Earlier, we had this to get fresh local envs. And got rest of the envs from cache.

We could either do that, or to keep things simple, we can get fresh envs (both local and global) in 2. by passing ignoreCache: true when calling interpreterService.getInterpreters here. It'll only be done once per workspace and once per session, and so should not be much expensive.