Add an end-to-end test and run it through CI about brownify HOT 1 CLOSED

This is now working. The test with no parameters set is optimized to run on a local system for quick testing with a simple pass/fail interface and a log file for details. It can have a flag passed in to log to the console for CI. It can also have different URLs or recipes provided, which might be useful in the future if we want to test our recipes more extensively.

I didn't have a great way to test the CI job without simply committing it and seeing what happened, but I now have most of the issues worked out. The one minor issue left is that we cannot use pip dependency caching for now. It seems like the Github action that supports pip dependency caching only supports it if the project tracks dependencies in a requirements.txt file. In our case, dependencies are tracked in a setup.cfg file. This doesn't prevent our job from running, but dependency caching would help speed things up.

The other issue is that #23 is still outstanding. I think this project is still in a place where we don't need to move heaven and earth to keep things working at all times. I am tracking when that merge request goes into pytube, and when it does I will upgrade. In the mean time, the CI runs of the test will fail.

from brownify.