Custom mitmproxy start skript and venv setup

[zner0L]

We should move the mitmproxy events addon and mitmproxy setup to a custom script that starts mitmproxy and sets up all the addons. This way we have more control and don't need the user to download scripts for themselves.

To manage our other python dependencies, we should create a postinstall script that creates a venv with all needed dependencies.

[zner0L]

It seems that extending the PATH globally doesn't work in execa(), which seems plausible since it runs in a child process. So what we need is to pass the venv path to appstraction, so that we can set it there as well.

Also, one problem might be to determine where the venv is actually created. During development, I wan the venv to be in .venv in the root folder, which is one layer below the src folder, but when I build it, the .venv folder needs to be on the same level as the index.js.

[zner0L]

Ah, nervermind. The dist/ directory is at the same level as the src/ directory, of course.