Restructure the parser to be Amenable to the Generator Linking issue and the Segmenting issue

[JamieLine]

Links to #26, #6 (mainly the predicate test), #21

Broadly

• [ ] Replace the current templates with segments, which are generic and perform a specific task. E.g. Every test will run the code in a for loop
• [ ] The templates can then be reworked to be defined in terms of segments + small connective tissue (unique functionality should ideally take its own segment, even if it will only be used once)
• [ ] The Create{Type}Test functions can then be decomposed into parts which populate Segments from some small object, created from the original spec. This will probably include having some MicroParsers which can do things such as "read an Index-Value Pair" or "Get the name and types associated with a function".
• [ ] Create a userland include which presents all of the names of things that show up in a test, and have that userland include be the canonical source for all "exposed api" names. E.g. the generators array, or the results array.
• [ ] Allow a test that references those "exposed api" names to be interpreted correctly. (Potentially a trivial side-effect of the above, possibly not)
• [ ] Once the predicate test in #6 is complete, replace UnmaskedStabilisingSetTest and UnmaskedAlwaysReturnValueTest with predicate test redefinitions.

[JamieLine]

Mockup of Predicate Test Template

ADDITIONAL_INCLUDES
#include ...
#include ...

bool FUNCTION_NAME():
  SETUP_INFRASTRUCTURE

  for (NumTests in [0, NumTestsToRun)) {
    SETUP_GENERATORS
    STORE_FUNCTION_VALUE
  }

  bool Passed = CREATE_PREDICATE_CALL;

  OUTPUT_INFORMATION

  return Passed;
}

[JamieLine]

The new layout will probably want to look something like this

Directory Structure

TestCreator/
  MicroParsers/ (Read specifications in)
    ParseIndexValuePair.h/.cpp (Likely no validation here, the Big Parser has more chance to handle any issues)
    ParseFunctionNameAndTypes.h/.cpp
    ParsePredicate.h/.cpp
    ...
    ...
    ...
  Structs/ (Intermediate representation)
    IndexValuePair.h
    Predicate.h
    ...
    ...
    ...
  SegmentWriters/ (return replacement for an individual segment)
    WriteSetupInfrastructure.h/.cpp
    WriteAdditionalIncludes.h/.cpp
    ...
    ...
  TemplateWriters/ (actually writes a full test to a file)
    WritePredicateTest.h/.cpp
    WriteTestRunner.h/.cpp
    ...
    ...
  Parser.h/.cpp (takes in someone else's file and makes all the tests as a vector of `GeneratedTest` objects which have their own write to file method to call later)
Main.cpp (instructs the parser to go over every needed file, then directly calls `WriteTestRunner` which uses that vector, then tells `FilesystemHandler` to write it all to disk)
FilesystemHandler.h/.cpp (utilities to read from and write to the filesystem, including writing the vector of tests to appropriate roles and eventually scanning a directory recursively)