chore(consensus): bump lighthouse to v8.2.2 (#580) (#581)

v8.2.2 is a high-priority release containing fixes for several security
vulnerabilities. The upstream update-priority table lists "High" for beacon
nodes; the security content is withheld until uptake is sufficient.

- pin sigp/lighthouse v8.2.1 -> v8.2.2 for consensus-gnosis
- record why the swap is drop-in and why it must not trigger a resync

No database schema migration and no breaking CLI changes upstream, so this is
a tag swap against the existing datadir. Upstream notes an open data-column
backfill OOM affecting Gnosis on every release up to and including v8.2.2
(fixed in v8.3.0), which is why an unnecessary resync must be avoided.

Author: leinss

docker/docker-compose.gnosis.yml

@@ -103,7 +103,12 @@ services:
 
   consensus-gnosis:
     container_name: consensus-gnosis
-    image: sigp/lighthouse:v8.2.1
+    # v8.2.2 is a high-priority release fixing several undisclosed security
+    # vulnerabilities; beacon-node update priority is "High". No schema
+    # migration and no breaking CLI changes, so the tag swap is a drop-in and
+    # must NOT trigger a resync — data-column backfill can OOM on Gnosis until
+    # v8.3.0, and that affects every release including the one we run today.
+    image: sigp/lighthouse:v8.2.2
     restart: always
     depends_on:
       nethermind-gnosis: