Testing: Consolidate the testing libraries
The testing suite currently builds several libraries. This is necessary to exercise some of the less-common paths of the interpreter. It was a strategy I chose because I was at the tail end of a release (and it was an even release).
I'd rather have the testing system build a single library. That one library would be composed of multiple dynaload tables/info tables. It's okay to do that, because the tables are namespaced. All that I would need is a 'main' file to load the files that are generated.
I'll do this one after touching upon the import plumbing as described in #393 (closed).