lv2: use brewed python

[alebcay]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

This PR tackles a number of concerns with the lv2 formula.

• The build system (waf) was using macOS system Python (/usr/bin/env python) to run. Rewrite shebangs (and any included wscripts) to build using [email protected]
• One of the components that are shipped #{bin}/lv2specgen.py needs Python at runtime. It also needs several Python modules to be present. Create a virtualenv and include the necessary modules; rewrite shebangs to use the virtualenv Python. (AFAICT, this was broken previously, unless you happened to have the necessary dependencies installed where system Python can find them)
• Add a test block to check that the necessary Python modules are present, and to check the lv2 framework itself by building a small example plugin against it

[alebcay]

Also - considering that lv2 doesn't really need Python at runtime, but only lv2specgen, I'd be open to making an lv2specgen formula (especially seeing as some other lv2 dependents still seem to have transitive runtime dependency on [email protected]). Another option is to have lv2 use [email protected] for now and then migrate it later, to avoid the audit conflict.

[BrewTestBot]

🤖 A scheduled task has triggered a merge.