Interpreter Schema Generation v2

In this PR, we rework the way that the interpreter generates a schema based on the underlying interpretations.

Changes:

Pre-initialization check for schema correctness given VALIDATE_PIPELINE_SCHEMA environment variable is set. This schema introspection fix assumes that there is only one source node to be interpreted under any ingest. A check is made for the following:
- Interpreter: Only one of the before iteration phase or interpretations phase can generate source nodes.
- MultipleInterpretationPass: If one of the passes contains a source node, all of the other passes must contain a source node.
- InterpretationPass: Only one of the interpretations can assign a source node.
- SwitchInterpretations: If one of the branches contains a source node, all of the other passes including the default branch must contain a source node.
For GraphQL schema generation, LocalDateTime objects are now DateTime objects.
The before iteration interpretations are now accounted for within the schema introspection. (We acknowledge that either the before iteration and interpretation phases can act as source node creators.)
Introspection is now broken down into context levels for each component that expands schema from children. For example:
1. Each pipeline has their own isolated context level.
2. For a Multiple Interpretation pass, each interpretation pass has their own context level that is distinct but inherits data from the interpreter (i.e if there is a before iteration phase with relationships).
3. For a switch interpretation, each {key: interpretations}, has their own context, ONLY if it is a source node generator. otherwise, each pass is added to the overall interpreter context.
The switch interpretation now represents the interpretations for each key as an interpretation pass.
Source node creators are now added to the end of the schema generation process.

Additional work/Unsolved Problems:

Key matching between switch interpretations within a reachable context. If keys match between switch interpretations at different context levels, we should be able to isolate the context for those relationships.

For instance:

switch:
  key: A
    - some relationship A
  key: B
    - some Relationship B 
switch:
  key: A 
    - some source node A
  key: B
    - some source node B

In the schema generation, source node A will involve both relationship A and relationship B, even though it is not possible for source node A to have relationship

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 97.87%. Comparing base (ee0c427) to head (c6d3927).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #333 +/- ## ========================================== + Coverage 97.80% 97.87% +0.07% ========================================== Files 143 144 +1 Lines 5001 5136 +135 ========================================== + Hits 4891 5027 +136 + Misses 110 109 -1 ``` | [Flag](https://app.codecov.io/gh/nodestream-proj/nodestream/pull/333/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=nodestream-proj) | Coverage Δ | | |---|---|---| | [3.10-macos-latest](https://app.codecov.io/gh/nodestream-proj/nodestream/pull/333/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=nodestream-proj) | `97.87% <100.00%> (+0.07%)` | :arrow_up: | | [3.10-ubuntu-latest](https://app.codecov.io/gh/nodestream-proj/nodestream/pull/333/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=nodestream-proj) | `97.87% <100.00%> (+0.07%)` | :arrow_up: | | [3.10-windows-latest](https://app.codecov.io/gh/nodestream-proj/nodestream/pull/333/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=nodestream-proj) | `97.83% <100.00%> (+0.07%)` | :arrow_up: | | [3.11-macos-latest](https://app.codecov.io/gh/nodestream-proj/nodestream/pull/333/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=nodestream-proj) | `97.87% <100.00%> (+0.07%)` | :arrow_up: | | [3.11-ubuntu-latest](https://app.codecov.io/gh/nodestream-proj/nodestream/pull/333/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=nodestream-proj) | `97.87% <100.00%> (+0.07%)` | :arrow_up: | | [3.11-windows-latest](https://app.codecov.io/gh/nodestream-proj/nodestream/pull/333/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=nodestream-proj) | `97.83% <100.00%> (+0.07%)` | :arrow_up: | | [3.12-macos-latest](https://app.codecov.io/gh/nodestream-proj/nodestream/pull/333/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=nodestream-proj) | `97.87% <100.00%> (+0.07%)` | :arrow_up: | | [3.12-ubuntu-latest](https://app.codecov.io/gh/nodestream-proj/nodestream/pull/333/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=nodestream-proj) | `97.87% <100.00%> (+0.07%)` | :arrow_up: | | [3.12-windows-latest](https://app.codecov.io/gh/nodestream-proj/nodestream/pull/333/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=nodestream-proj) | `97.83% <100.00%> (+0.07%)` | :arrow_up: | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=nodestream-proj#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

nodestream-proj / nodestream

Interpreter Schema Generation v2 #333

Codecov Report