stack-encrypt conformance: enroll EQL and JSON/SQL operation profiles #1476

Existing JSON and PostgreSQL suites need named requirements and shared inputs, beyond the current NoTargets record profiles.

Acceptance:

• Define EQL resolver/catalog capability cases and JSON write, query, extraction, subtree, element-match and predicate-match operation profiles.
• Pin supported predicate grammar, unsupported-operation diagnostics, null/missing behavior, tamper handling and request-bound reads.
• Reuse current Rust/Go/SQL suites and fixture paths; add shared vectors where evidence is missing.
• Compare behavior with independent PostgreSQL plaintext oracles and document intentional differences, including randomized projection order.
• Record engine and SQL bundle versions and require the relevant database lane.

Build on #1471–#1474. Coordinate typed API evidence with #1459; enroll existing operations rather than reimplementing the already-landed Go JSON work.

Plan: conformance roadmap and API redesign #1365.