feat(lattice): add fragment adapter registry

[mgazza]

Summary

• add a brand-neutral registry for local and cloud integrations that publish Lattice fragments
• discover publishers through the structural lattice_fragment_adapter() contract
• persist immutable provider snapshots with generation and semantic-fingerprint fencing
• let every registered integration invalidate the aggregate compiler when its observed state changes
• coalesce invalidation bursts into fresh-read compilation with one bounded follow-up when state changes during a compile
• keep registry membership frozen once compilation starts and reject runtime unregister attempts
• keep discovery and all production wiring default-off

Safety properties

• invalidation never mutates compiled configuration directly; it only requests a fresh read of every registered fragment
• OFFLINE, DEGRADED, removal, restart, feedback, CAS-conflict, and mid-compile invalidations all preserve fail-closed state
• same-generation semantic mutation is rejected
• adapter state and the compiler's observed cursor remain generation/fingerprint bound
• failed adapter CAS leaves the compiler invalidated, so it cannot publish from an uncommitted snapshot
• no configuration materializer, MQTT subscription, Home Assistant callback, or control write is wired

Verification

• python3.9 -m unittest apps/predbat/tests/test_lattice_fragment_adapters.py apps/predbat/tests/test_lattice_autoconfig.py apps/predbat/tests/test_lattice_compiled_publication.py — 89 passed
• Black, Ruff, cspell, and pre-commit checks passed
• GitNexus staged change detection: LOW, exactly two files, zero affected execution flows

Stacked on #4326. Tracks Predictive-Cloud-Ltd/predbat-saas-infra#561 and #466.