Task: Seed the stress shift families and shift types

The database refuses a stress shift family or shift type ORE does not have.

• Seeded lookups hold the shift families and shift types stress.xsd defines, derived with the command recorded.
• stress_test_shift.family and stress_test_shift.shift_type refer to them, and an unknown value is refused on insert.
• The stress test corpus and database round trips still pass.

• The families are the sixteen children of the stresstest type in external/ore/xsd/stress.xsd, apart from Date. They are exactly the sixteen strings the stress test mapper writes into stress_test_shift.family.
• The shift types are the shiftType enumeration in external/ore/xsd/ore_types.xsd: Relative, Absolute, EqualTo. The sensitivity configuration uses the same enumeration, so the lookup is named shift_type, not after stress.
• Both are analytics lookups seeded for the system tenant and readable by every tenant, as pricing_engine_type is, and the shift's foreign keys resolve under the system tenant.
• No stress database round trip existed, so this task adds one, over the corpus file that applies shifts in ten families and uses all three types, with a refusal case for each column and a test that pins both seeds to the schemas.

Every number this task claims about a tree, with the command that produced it and the commit it was measured at. A number without both is not a measurement, because a clean-up record describes a tree and trunk moves under a branch: a consumer count, a gate's component count and a suite's size all change with no code changing, and the reader of a bare number cannot tell which tree it came from. Where the raw output matters, put it in an evidence/ file beside the task and name that file in the Command column.

• stress_test_shift also carries an extras column of name and value pairs, which the story's acceptance rules out. It is outside this task, which is about the family and the shift type: Replace the stress shift extras with typed rows.

Manual QA scenarios (scaffolded via compass add test_scenario) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.

• New analytics lookups stress_shift_family (16 rows) and shift_type (3 rows), seeded for the system tenant from stress.xsd and ore_types.xsd, readable by every tenant.
• stress_test_shift.family and stress_test_shift.shift_type are soft foreign keys resolved under the system tenant; an unknown value is refused on insert.
• New tests: the seeds pinned to the schemas; a stress database round trip over MarketRisk/Input/stresstest.xml, ten families and three types, compared with the mapper's in-memory round trip; one refusal case per column.
• Migration analytics_stress_shift_vocabulary_migration.sql for existing databases, refusing while a current shift names a value outside the schemas.
• Build clean; ctest 89/89 after a database recreate.
• Found on the way and filed: the shift's extras column of name and value pairs, and the mapper dropping an empty family element, in Replace the stress shift extras with typed rows.