Reword the Molecule scenario comments

They were hard-wrapped at 80 characters, broke mid-parenthesis, and spent lines
restating what the code below them does.

Rewrapped at natural boundaries instead, with the narration dropped and only the
reasons, gotchas and surprises kept. Section dividers stay - they delineate long
plays rather than narrate them.

Comments only; no scenario behaviour changes.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SEH3vxYSQ5SV4N5z61eyGT

molecule-shared/vars.yml

@@ -1,13 +1,11 @@
 ---
-# Helper container images the scenarios use for probing. They live here rather
-# than inline in each verify.yml so that there is one pin per image instead of
-# one per role, and so Renovate can see them (see the customManager in
-# .github/renovate.json).
+# Helper container images the scenarios use for probing. Here rather than inline in each
+# verify.yml, so there is one pin per image instead of one per role, and so Renovate can see
+# them. See the customManager in .github/renovate.json.
 
-# Used to reach a role's container over its own container network. A helper is
-# needed because the role publishes no host port - exactly as in a real
-# deployment - and publishing one for the test would collide between scenarios
-# running in parallel.
+# Used to reach a role's container over its own container network, because the role publishes
+# no host port - exactly as in a real deployment. Publishing one for the test would collide
+# between scenarios running in parallel.
 # renovate: datasource=docker depName=docker.io/curlimages/curl
 molecule_shared_image_curl: "docker.io/curlimages/curl:8.11.1"