New Easy-Wav2Lip.bat for venv usage

[anothermartz]

My baby's got the venvs!

I managed to get around what was causing issues when using a venv (python virtual environment) to set up Easy-Wav2Lip the first time I tried.

Advantages of using a venv:

• Doesn't mess with your existing python install that may want to use other versions of the same modules used here
• Allows installations of multiple python versions for when other projects require them
• Allows easy complete un/reinstallation of Easy-Wav2Lip for if things go wrong (just delete the Easy-Wav2Lip-venv and Easy-Wav2Lip folders and it's like it never happened and you didn't just spend 3 hours trying to make a video of Ben Shapiro performing rapper's delight).

Disadvantage:

• A bigger install size if other projects use the same modules as this (unlikely)

Also I got rid of VS BuildTools C++ module installation!

It was the biggest pain for installation as it wasn't completely obvious to tick the C++ box and it took ages to install and it turns out it was completely unnecessary if pip was updated, which I already took care of so whoops!

If you don't need it for anything else, uninstall VS BuildTools to save yourself some storage space.

Python 3.10.11 and Git now install automatically so the whole operation is completely automated!

From a fresh install, even without any prerequesits, you launch Easy-Wav2Lip.bat, confirm you want it to install in this location and it'll do it all entirely on its own! (takes a while and downloads a bunch!)

Also, commandline arguments

Unrelated to Easy-Wav2lip.bat but I recently updated run.py to allow for the following commandline arguments:
-video_file
-vocal_file
-output_file

usage (all commands are optional):
python run.py -video_file "filepath" -vocal_file "filepath" -output_file "filepath"

Things not specified here will still be taken from config.ini

If you want any more commandlines I could do that too but I'm not expecting this usage to be very widespread.