PLT-7204 Part 2: Dynamic query

[jhbertra]

• Adds new library hasql-dynamic-syntax for AST-based dynamic query generation
• Adds schema types and tables for marlowe schema.
• Rewrites getPayouts to use hasql-dynamic-syntax

Pre-submit checklist:

• Branch
  • Tests are provided (if possible)
  • Test report is updated (if relevant)
  • Commit sequence broadly makes sense
  • Key commits have useful messages
  • Relevant tickets are mentioned in commit messages
  • Formatting, PNG optimization, etc. are updated
• PR
  • Self-reviewed the diff
  • Useful pull request description
    • Review required
    • Substantial changes to code, test, or documentation
    • Change made to Marlowe validator (@bwbush and @palas must be included as reviewers)
    • Review not required
    • Minor changes to non-critical code, documentation, nix derivations, configuration files, or scripts
    • Formatting, spelling, grammar, or reorganization
  • Reviewer requested

[bwbush]

This looks good, but there was too much code in the new package for me to review in great detail and there are no tests in the new package's test suite yet.

How were the golden tests generated and checked for correctness? Are they just to detect regressions?

Finally, can we add a changelog entry to runtime for this. Are there no API or breaking changes?

[jhbertra]

This looks good, but there was too much code in the new package for me to review in great detail and there are no tests in the new package's test suite yet.
Yeah, I didn't think the new code was particularly high-risk for correctness because it was largely copied-and-pasted from existing high-assurance code (and the types are pretty good here at eliminating errors). At some point, I will write tests for these, for now it's implicitly tested by the integration tests.
How were the golden tests generated and checked for correctness? Are they just to detect regressions?
These are generated in GetPayoutsSpec.hs. Correctness is less the goal as change detection and accurate documentation off what SQL is generated by the code under various configurations. The correctness is checked by the integration tests.
Finally, can we add a changelog entry to runtime for this. Are there no API or breaking changes?
No changelog needed - it's an internal change