Consume pinned portable v5 rule releases

[zhaobozhen]

Consume a pinned portable v5 Rules release instead of maintaining an independent rule import contract. Verify the immutable artifact and metadata before generating shared lookup, localized-detail and icon data, retaining the existing web/Worker behavior and lazy loading.

• Add an explicit updater and an own-repository update-PR workflow with version/source and content-change summaries.
• Keep a verified local portable 45 bootstrap for reproducible builds before the first remote release. Normal updates reject changed content under the same version.
• Preserve all portable UUIDs, details, SVGs and matching semantics; Android's compact database does not alter bot content.

Validation: targeted Node/Python importer tests, 19 shared matching fixtures, 2,736 literal lookups, integrity/locale/cache checks and offline generation passed. Pages build and all size budgets passed (core 483.1 KiB, details 2.18 MiB, icons 452.8 KiB, total JS 3.48 MiB, four initial requests). Portable entries are unchanged except release metadata. Unrelated UI/runtime tests and Worker dry-run were not repeated for the final metadata refresh; no deployment, Telegram or KV operation was performed.

After Rules 45 is published from 7b0a6f92806de7b6c7cf578049b28b555564c223, run npm run rules:update -- --manifest to replace the local bootstrap with the verified remote lock, then run check/build/size gates. Merging to main invokes this repository's existing production deployment workflow; review that rollout deliberately.

Related Rules migration: LibChecker/LibChecker-Rules#1386