feat(abt): speed up analyses battery with async analysis

[y3rsh]

Overview

Remove cruft from generate_analyses.py and analyze against n containers in a ThreadPoolExecutor.

• Works locally
• Works in CI

[SyntaxColoring]

TY! Here's a Python coding practices suggestion, but it doesn't block merging.

[SyntaxColoring]

For future reference, as a general practice, I think we should avoid stringifying exceptions like {e} or str(e). It can be okay for certain exception types, but in the general except Exception case, like here, it can give you confusing and incomplete information. For example, if a KeyError came from some_dict["foo"], this would only print:

An error occurred during analysis: foo

If you're using logging, you can do exc_info=True to automatically include full exception information, like:

except Exception:
    log.warn("An error occurred during analysis.", exc_info=True)

If you're not using logging, like in this case, you can use something like traceback.print_exception() (output to a file) or traceback.format_exception() (output to a string).

[y3rsh]

Thank you for the suggestion. Helped me in another spot today 😊
I will merge this but will fix this to use Rich console exception printing in another PR. It is totally wrong.