User specified Python environment is not prioritized in Python Path

Version and Platform (required):

• Binary Ninja Version: 3.4.4133
• OS: Ubuntu
• OS Version: 22.04
• CPU Architecture: x64

Bug Description:
When a user manually sets the "virtualenv" of their Binja's plugin, they expect that Python to have priority in package lookup against the builtin Binja Python; however, it is not prioritized.

Steps To Reproduce:

1. Open Binja and set up your Python to be something like this:
   
2. Restart Binja
3. Go to the Python interpreter in Binja and type import sys; sys.path, this should result in something like:

['/home/mahaloz/.binaryninja/repositories/official/plugins', '/home/mahaloz/.binaryninja/repositories/community/plugins', '/home/mahaloz/.binaryninja/plugins', '/home/mahaloz/.binaryninja/python310/site-packages', ...]

Notice that the last entry in the path is /home/mahaloz/.binaryninja/python310/site-packages, which means when a user has a library installed on the Binja python, that one will always be chosen. Whenever a user sets their Python env manually, it's expected that their packages would be chosen when this happens.

Expected Behavior:
Whenever a user sets their Python env manually, it's expected that their packages would be chosen when this happens. After they do this change, they should see their site packages before Binjas in the Path.

Screenshots:
Show above.

Additional Information:
Linking BinSync issue so both can close when this is fixed: https://github.com/binsync/binsync/issues/241

Start by reproducing the configured virtualenv behavior in Binary Ninja's Python interpreter with import sys; sys.path, as described in the issue. Trace the plugin environment setup and verify that the user-selected environment's site-packages appear before Binary Ninja's built-in site-packages when the issue is fixed.