Qualify SQL Moose names and make cross-schema lookup unambiguous

[deem0n]

Problem

Distinct SQL tables in different schemas inherit the same short mooseName while claiming hasUniqueMooseNameInModel. entityNamed: returns the first match. Routine overloads and contained names also collide.

Found during the 2026-09-20 FAMIXNGSQL/Moose 13 compatibility audit.

Implementation scope

Define stable, escaped names using SQL ownership and routine input-type signatures; preserve short display names; invalidate cached names correctly.

Implementation PR target: deem0n/FAMIXNGSQL, in the deem0n fork first. Keep this issue separate from the other v3.0.0 fixes. The PR must explain the previous failure, resulting behavior, compatibility implications, and actual validation.

Acceptance criteria and tests

Cross-schema table/view lookup; columns and constraints with different owners; overloaded routines; quoted identifiers; rename/reparent behavior; MSE round trips and generator stability.

• Regression tests demonstrate the reported problem and pass with the fix.
• Relevant existing tests pass; validation environment and limitations are recorded in the PR.
• A separate implementation PR is linked here and reviewed.
• Integrated v3.0.0 acceptance is verified before this release blocker is closed.

Release

Part of the v3.0.0 milestone. An open PR is not a completed fix; release qualification is tracked separately.

Implementation

#26

Combined qualification: #32. The implementation is available for review; this issue remains open until its integrated release acceptance is verified.