Task: Generation configs move to oresmd URIs

Make the synthetic generation configs identify market data by oresmd URI. fx_spot_generation_config and ir_curve_generation_config each carry one oresmd_uri; the component columns drop; validation moves to the oresmd layer; the Qt editors round-trip URIs.

• fx_spot_generation_config: ore_key becomes oresmd_uri; base_currency_code and quote_currency_code drop; the pair comes from the parsed identifier; the base != quote check lives in the parser.
• ir_curve_generation_config: currency_code, index_family, tenor, and role become one oresmd_uri.
• Validation (family list, tenor rules, role) lives in the oresmd layer.
• FxSpotRateEditor and IrCurveEditor edit and save URIs.
• ir_curve_template_entries stays unchanged: the instrument grid is not identity.

(Implementation strategy. Written when work starts; key decisions are distilled into the parent story's * Decisions at close, but the plan itself stays — it is the historical record of what we did.)

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

Abandoned at sprint 25 close, as part of the reset to one approach for sprint 26. The work is not in the sprint 26 plan. The done tasks stay as the record of what shipped.