Create a consume mode for `t8n`

Right now t8n is invoked by the EELS system every time a fixture needs to be executed as a test case. The startup time for this causes significant lag that greatly increases run-time for executing the fixture tests. It would be better if t8n was a separate service which started up once, and then accepted requests to process fixtures either as a collection, or individually.

Refactor **t8n** code to be an independent service that runs in the CI alongside EELS. It should accept requests sent to it, parse the request JSON data (the fixture(s)), execute the test in EELS, and then return a result for the submitted collection of fixtures.