Sweep pre-template-fix entities: add security definer and active-rows bootstrap filter

All ores_refdata_validate_*_fn functions and insert trigger functions generated before PR #1300 (commit 1cb85c9a, sprint 21) carry two architectural gaps: they lack security definer set search_path = public, pg_temp, and their bootstrap pass-through checks for any rows rather than active rows (valid_to = ores_utility_infinity_timestamp_fn()). The affected entities include currencies, rounding_types, monetary_natures, currency_market_tiers, party_id_schemes, party_statuses, party_types, book_statuses, contact_types, and purpose_types — all 10 entities currently generated from sql_schema_create.mustache. The template has been fixed in PR #1300; future entity generations are correct automatically. This capture tracks whether a coordinated sweep of the existing files is warranted before they are each naturally recommissioned.

The two gaps are architectural correctness issues: security definer + set search_path prevents search-path injection from a service role with a manipulated path; the active-rows bootstrap filter prevents a confusing "Must be one of: (empty list)" error when a table has only soft-deleted historical rows. Both are now documented as mandatory rules in PostgreSQL: Database Architecture and Conventions and as checklist criteria in Domain entity evaluation checklist. The analysis and rationale live in Commission: country § Analysis.

The commissioning pipeline will repair each entity naturally (each commission story's verify-SQL task now checks for these items via the checklist). A proactive sweep would close the gap sooner but is only warranted if any of the affected entities are used as soft-FK targets in production before they are commissioned.

• PR #1300: Commission country: verify SQL, add validate_country_fn, document trigger categories
• Commit: 1cb85c9a — fix validate fn security definer and bootstrap valid_to filter

• Commission: country — Analysis section documents the rationale in full
• PostgreSQL: Database Architecture and Conventions — canonical rules
• Domain entity evaluation checklist — checklist criteria that ensure future commission stories pick this up
• sql_schema_create.mustache — the fixed template