"python" in activated virtualenv is not used.

[ericsnowcurrently]

In my workspace folder I created a virtualenv with Python 3.7 in a new .env directory. In VSC I switched to that interpreter and it shows the proper version in the status bar. When I run "Python: Create Terminal" (with no terminals open already), it creates a new terminal and runs (sources) what appears to be the correct activation script. However, if I run python -v it shows me "2.7.15", which is the system Python 2 binary. If I run the virtualenv's python by using the full path into the virtualenv's bin directory, it works as expected.

[DonJayamanne]

Duplicate of #4434 being tracked in #4568