Assess if TestFramework needs pre-execute and post-execute steps

I'm thinking maybe a list of actions that a test author can register to get advanced logging on before and after states of tests and test blocks, pushing/fetching information from a DB, etc., and generally things that need to live between test setup/teardown and creating the actual test blocks to run.

To make this worth it, we may need to add some helper methods to fetch things like the names of test blocks (in order), any traits associated with the test case, maybe inputs/outputs, etc. As one example, something like:

TestBuilder.RegisterPreTestCaseAction(() => MyHelpers.SaveTestBlocksToDb(TestBuilder.FetchATestBlockMetadata()));

Review the TestFramework and TestBuilder execution flow around test setup, teardown, and test-block creation. Determine whether pre- and post-execute actions and metadata helpers are needed; done means a documented design decision with a defined scope and behavior.

Written by the indexing model from the issue text.