fix(query): use supplied ontology for security filters

What does this MR do and why?

Queries compiled with another ontology could omit required namespace filters or filter nonexistent columns. The compiler now uses that ontology consistently. Serving and readiness stay unchanged.

Related Issues

Relates to #184 (closed). Next slice of !2433 (closed), stacked on !2434 (merged).

Testing

598 compiler/ontology tests and 163 local integration tests pass, along with Clippy, formatting, and docs checks. Both regressions fail on !2434 (merged).

Performance Analysis

• This merge request does not introduce any performance regression. If a performance regression is expected, explain why.

Agent context

Review tightened regression coverage for archive renames, alternating ontologies, and scoped joins. It also removed a redundant wrapper. Security contract. Performance was not benchmarked.

Local logs: /tmp/orbit-ontology-compiler-green.log, /tmp/orbit-ontology-compiler-local.log, /tmp/orbit-ontology-compiler-clippy.log, /tmp/orbit-ontology-compiler-red.log.

Next: archive-validated promotion/rollback, then active-schema serving and readiness.