feat(lattice): publish GE Cloud topology fragments

[mgazza]

Summary

• add a pure, explicitly enabled GivEnergy Cloud Lattice fragment publisher
• adapt versioned discovery, device, liveness, and removal snapshots into the common durable fragment surface
• invalidate the shared compiler whenever an accepted integration change advances the provider generation
• publish deterministic provider-local topology and REFERENCE-only serial/UUID identities
• compose Gateway and GE Cloud views of the same physical device through strong serial identity
• reject stale replay, version reuse with changed content, identity collisions, and ambient resurrection after removal

Safety

• default off and not registered in the production component graph
• no changes to the live GE Cloud polling integration
• no PredBat configuration mutation, materializer callback, cloud write, or control write
• no PRIMARY/CONTROL roles, capabilities, or config projections
• removed integrations require a future explicit re-enrol operation

Validation

• 95 focused and adjacent tests pass on Python 3.14
• 42 focused and adjacent tests pass on Python 3.9 and Python 3.14 in the implementation review
• Black, Ruff, cspell, pre-commit, and diff checks pass
• GitNexus: MEDIUM risk, 46 additive symbols and one new internal flow

Stack

• base: feat(lattice): adapt Gateway topology fragments #4331
• programme: Predictive-Cloud-Ltd/predbat-saas-infra#466
• fragment compiler/materializer tracker: Predictive-Cloud-Ltd/predbat-saas-infra#561