Document Schemas for SQL Rule type

- For each possible input data source, we will need to define the SQL schema and make available for the authors.
- For example, study data, define xml (dataset, variable, and VLM metadata), library standards data, ct data, study data metadata (dataset and variable)
- It should not be necessary to convert these sources to SQL tables or design the schema, because this should already be done by the SQL refactoring.
- There may be a step required to make these source tables available in the operations and check
- Since SQL rule type is replacing the ability to use different rule types, we may need to simulate rule types with operations

The issue names no files, tests, or entry points. Start by mapping the existing SQL refactoring and the operations and check flows, then inventory the listed input sources and their available schemas. Done means the required source schemas are documented and their availability and any rule-type simulation needs are clearly specified.

Written by the indexing model from the issue text.