chore: rename prisma-models to query-structure

[Weakky]

Overview

Preparatory core refactoring to support joins through FieldSelection and not ReadQuery.

• Moves Filter, QueryArguments, and *Compare interfaces to query-structure
• Renames prisma-models to query-structure (naming up to debate) (rename needed to better reflect the larger scope that prisma-models now encompasses)

Goal:

• Enable abstracting aggregation selections in SelectedField, thus removing the need for RelAggregationSelection (still defined in query_connector).
• Enable abstracting relation selections (for joins) in SelectedField

FWIW, uncle gippity suggested the following other namings for the new query-structure crate:

• query-framework: Suggesting a foundational set of tools and abstractions for query construction.
• query-schema: Reflecting the definition and organization of query elements.
• query-architecture: Indicating a comprehensive design or blueprint for query elements.
• query-composition: Highlighting the arrangement and combination of query components.
• query-blueprint: Conveying the idea of a detailed plan or model for query construction.
• query-fabric: Suggesting the underlying fabric or structure of queries.~
• query-skeleton: Indicating the basic structure or framework of a query.
• query-template: Implies a predefined structure or pattern for query elements.

[codspeed-hq]

CodSpeed Performance Report

Merging #4458 will not alter performance

_{Comparing chore/join-prepation-work (739ba4d) with main (0a59e97)}

Summary

✅ 11 untouched benchmarks

[miguelff]

query-structure is a better name than anything GPT has imagined.

[Weakky]

query-structure is in fact another suggestion from uncle gippity 😆