fix(model): polymorphic associations find underscore-shaped columns

[bpamiri]

Replaces #4420, which closed automatically when its base branch (#4398's) was deleted on merge. #4398 is in develop now, so this PR targets develop.

Polymorphic associations find underscore-shaped columns

A polymorphic association declared without foreignKey / foreignType fixed its columns to <name>id / <name>type at registration, before the schema is read. That covers belongsTo(polymorphic = true) and hasMany() / hasOne() with as. An app whose schema uses the underscore shape, as t.references(polymorphic = true) writes it when useUnderscoreReferenceColumns is on (the wheels new default), threw key [<name>id] doesn't exist on first use.

Non-polymorphic defaults already resolve against the schema at join time (#3337). This does the same for polymorphic ones:

• Registration records which polymorphic column names were derived; names passed as foreignKey / foreignType are never touched.
• On first use, $resolvePolymorphicColumns() checks the child's real columns. That's this model for a polymorphic belongsTo, and the associated model for hasMany / hasOne with as. It runs from the association methods, the include join and the nested-properties link.
• <name>id / <name>type win when they exist (including when both shapes exist). Otherwise <name>_id / <name>_type are used when they exist. When neither exists, the legacy default stays, and the existing error path reports it.
• If the child's columns can't be read (say the child model fails to load), the defaults are kept, a warning is logged, and nothing throws.
• The result is memoized per association, under a named lock with a double check.

Specs

vendor/wheels/tests/specs/model/polymorphicSchemaColumnsSpec.cfc runs on its own underscore-shaped tables, with models that pass no column names:

• create through hasMany and read back through belongsTo;
• hasMany reads and counts filter by the type column;
• an include join filters by the type column;
• create and read through hasOne;
• nested properties set both columns;
• the resolved names are recorded on every side;
• both shapes on one table: the legacy names win;
• a child model that doesn't exist: the defaults are kept and nothing throws;
• an explicit foreignKey with a derived foreignType, and the reverse: only the derived name resolves.

Every spec starts with the model classes forgotten, so each path resolves the columns itself. The include join and the nested link run as the association's first use, with rows inserted directly rather than through the association. Removing either call site makes its spec fail with key [notableid] doesn't exist; I checked that and then restored the code.

The legacy shape is covered by the existing polymorphic specs, which pass unchanged.

RED before the resolver: the schema cases error with key [notableid] doesn't exist.

GREEN:

• Lucee 7 + SQLite after merging develop: full suite 7101/7101.
• RustCFML: 7086/0.
• Complexity gate, consumer-docs check, guides build and verify-docs on associations.mdx (17/17) pass.

Docs

• basics/associations.mdx, "Column names": how the columns are found, with explicit names for anything else.
• .ai/models.md, consumer copy and template.
• A fixed fragment.

🤖 Generated with Claude Code

[bpamiri]

Source review: APPROVE at 5b305d9, with final approval pending the full matrix and current-head PR CI.

Compared with the previously reviewed resolver in #4420, the production changes are identical. The new specs clear the model cache before each case, exercise the include join and nested link as first use, and cover both mixed explicit/derived column-name combinations. The include case seeds rows directly rather than warming the association through a create call.

No new source blocker. Final verification will check the named schema-resolution specs in every matrix leg, plus the PR's own checks.

[github-actions]

Wheels Test Results

232 180 tests   226 996 ✅  1h 41m 5s ⏱️
 18 464 suites    5 184 💤
     32 files          0 ❌

Results for commit 5b305d9.

[bpamiri]

Final review: APPROVE at 5b305d9.

I read all 32 raw engine/database results from full matrix 37403150148 on this head: 577 bundles discovered per leg, zero failures/errors. polymorphicSchemaColumnsSpec passed all 10 named cases on every leg (320 passes, no targeted skips), including cold include/nested first use and both mixed explicit/derived combinations. RustCFML and the compatibility gate succeeded.

The reviewed resolver is unchanged from the earlier source approval. Current PR CI: 29 passed, 2 skipped (Update docs and Reviewer), 0 failed or pending. No remaining blocker.