Create a package to run ALKiln in an interview on someone's server

[plocket]

The user would install the package and thereafter have access to an interview they could run. At MVP, the interview would allow them to install an available version of ALKiln, pick tags for running the tests, and get the output of the tests.

The package needs a better name, but is already being worked on at https://github.com/plocket/docassemble-ALKilnInAPlayground. The finished functionality might be at MVP now. I think the major items missing, if we want to include them in MVP are:

• Set other env vars (like max time per step)
• Allow testing default project

Things that I think would be nice, but possibly not MVP:

• Convert the python code to a module? Can we avoid this? Nicer for us to not wait for reload with every tweak.
• Tell user if the version they have installed is the latest version?
• Add "restart this session"? So they don't have to make a new interview for every test if they don't want to.
• Coloring output: Cucumber formatter for some of it maybe https://github.com/cucumber/cucumber-js/blob/main/docs/formatters.md
• Only show debug_log.txt if there's no report.txt. Maybe same for GitHub tests. Or add more to the debug log.

The functionality that's already done includes these:

• Require user to be logged in before running interview
• Remove extra 'tmp' dir in unzipped zip
• Put report at top of summary files
• Use background action args
• Don't install if new version matches the old version. Just exclude it from the list of options? No, that'll be more confusing if they can't find what they're looking for.
• Delete unclosed... puppeteer browser folders? Files? puppeteer_dev_chrome_profile-zzzzz
• Choose version of ALKiln with cached version
• Show ALKiln version to user
• Clean up files no matter what
• Allow user to stop in the middle of the test and jump straight to output. See new revoke
• [auto deleting now] Bug: deleting goes back to output page before going to end
• start new session/interview
• Style results page. Scenario background color?
• Delete /tmp files after copying into da files (doesn't keep the folder structure, but I guess the zip does)
• Use dynamic server url
• Use dynamic project
• Add project name env var to alkiln cli version.
• Use dynamic user id
• Use dynamic tags

Future features:

• Show the user a live update of the console as the tests are being run. This would include output from tests that were stopped early. Right now, the suggestion is to create a Flask app for that - a huge change.

[plocket]

#661 is already for this. Closing as duplicate.