In SERVER-62995, we added a prettyprinter unit test. Some of the setup is specific and hardcoded to that particular test but we may want to support the addition of other tests (like SERVER-69842), and not require so much boilerplate.

It could be general in the sense that someone could make a some arbitrary piece of code, then a list of gdb commands to run and the regex to apply to the output. The frame work would be responsible for then building the tests, tagging them as a pretty-printer AIB test component, and also generating the launchers so there is a single no arg entry point to fit in our current unit tests framework. The launchers would ensure to setup the python environment.

Similar to our CppUnitTest builder in the SConscripts but with different inputs (the source, list of gdb commands, and regex applied to output, instead of just source files) (edited)