Generate versioned v5 rule artifacts from canonical sources

[zhaobozhen]

Rule imports currently require separately maintaining per-library JSON, SQLite, icon indexes and downstream versions. Introduce canonical library sources and a deterministic compiler/publisher so one validated source revision produces Android, portable and legacy compatibility artifacts.

• Android schema v5 contains only the seven matching columns plus priority, with metadata. Portable data retains UUIDs, localized details, SVGs and shared matching fixtures.
• Preserve existing rule IDs and cloud detail paths; import Android vectors and derive web SVGs with stable icon indexes.
• Validate pull requests and publish immutable data releases to rules-data, updating cloud compatibility data before advancing the manifest. SDK candidate definitions remain inactive.

Validation: eight producer/publisher regression tests, migration audit, and independent verification of all 2,832 rules, matching priorities and 2,687 cloud descriptions passed. Cross-consumer checks passed locally; the remote publication workflow has not been executed.

First release remains dataVersion 45. After merging to v4, manually run Publish rules data with bootstrap_source_revision=7b0a6f92806de7b6c7cf578049b28b555564c223. Preserve this exact commit in the remote until publication; substituting merge HEAD changes the locked artifact bytes. The automatic first run without this input intentionally refuses publication. Subsequent changed releases increment the data version normally.