inconsistent interpreter selected state after venv was created

[amunger]

Testing #23272

1. After the env was created and selected in the TPI, I see a notification that the env was selected but
   a. The toolbar item did not update, still says select interpreter
   b. A new terminal does not activate the new venv, nor does the current terminal ask me to reload
   c. running a python file does use the newly created venv

[eleanorjboyd]

This whole flow is re-done by the python envs ext so going to close this as stale