test(cascade_cols): update Healthcare ctx_id assertion to 2 (post-#364)

link_and_entity_type_id_resolution was written before PR #364's Codex P1
fix (`2089c1c`), when registry-created rows always carried
ontology_context_id = 0. That fix made RegistryState::append stamp the
seeded id from NamespaceRegistry::seed_defaults() — Healthcare = 2 — so
the MulThresholdProfile MEDICAL/CALLCENTER lookup at driver.rs:303-321
actually fires for Healthcare/WorkOrder/Medical rows instead of always
selecting DEFAULT.

The test assertion `== 0` is stale; the desired behavior is `== 2`.
Closes the pre-existing test failure flagged in the conflict-resolution
commit message. Listed in PR #369's deferred backlog as the Tier B
"per-row BindSpace.context_ids for driver.rs:311" follow-up — this is
the test-side; the BindSpace SoA layout change remains sprint-10.

Author: claude

crates/lance-graph-ontology/tests/cascade_cols_test.rs

@@ -86,5 +86,11 @@ fn link_and_entity_type_id_resolution() {
         .enumerate_first_with_entity_type_id(h.schema_ptr.entity_type_id())
         .unwrap();
     assert_eq!(resolved.public_name, "Patient");
-    assert_eq!(resolved.ontology_context_id(), 0);
+    // Healthcare is seeded to ontology_context_id = 2 in
+    // NamespaceRegistry::seed_defaults() — the Codex P1 fix in PR #364
+    // makes RegistryState::append stamp the seeded id onto SchemaPtr so
+    // the MulThresholdProfile MEDICAL/CALLCENTER lookup at
+    // driver.rs:303-321 actually fires for Healthcare rows. The
+    // previous `== 0` was written before that fix landed.
+    assert_eq!(resolved.ontology_context_id(), 2);
 }