Fix typo: only activate.* should be counted for virtualenvs

[collinmurch]

Recently ran into a QoL issue in VSCode where my Homebrew installations of python3 were being counted as "Virtual Environments". There are several Homebrew packages that install to the /opt/homebrew/bin directory (where Python does) that start with the pattern activate*.

For example, activate-global-python-argcomplete.

Really, we should only consider it a virtual environment directory if the activate script we look for has some arbitrary extension, not just starts with the string activate. Hopefully this can save people in the future from going down the rabbit hole I did.

[DonJayamanne]

Unfortunately on unix, the activation script can just be a file named activate without any file extension.
Hence cannot take this file as is.

Please can you file an issue for this. generally we start with an issue, then create a PR that resolves the issue.
In the Issue we can probably discuss the solution, as the current solution doesn't work

E.g. we could look for files like activate or activate., perhaps that should fix it.

Or perhaps we might need to revise the algorithm, e.g. clearly home brew should never be treated as virtual envs, even if they contain activation scripts.