fix(workflows): restore full context in Python version comments

Restored the detailed explanation about Python 3.13's hashlib.md5()
incompatibility with gyp. The full context is important for understanding
why we use 3.11 and what breaks in 3.13.

Author: jdalton

.github/workflows/build-sea.yml

@@ -338,6 +338,7 @@ jobs:
           # Use 3.11 to match Alpine 3.19 (Docker builds) which ships Python 3.11.14.
           # Python 3.13 breaks gyp with: TypeError: Strings must be encoded before hashing
           # At: tools/gyp/pylib/gyp/generator/ninja.py:813 hashlib.md5(outputs[0])
+          # Python 3.13 requires .encode() for hashlib, but gyp doesn't support it yet.
           # Using 3.11 ensures consistency across standard and Alpine builds.
           python-version: '3.11'
 

.github/workflows/build-smol.yml

@@ -348,6 +348,7 @@ jobs:
           # Use 3.11 to match Alpine 3.19 (Docker builds) which ships Python 3.11.14.
           # Python 3.13 breaks gyp with: TypeError: Strings must be encoded before hashing
           # At: tools/gyp/pylib/gyp/generator/ninja.py:813 hashlib.md5(outputs[0])
+          # Python 3.13 requires .encode() for hashlib, but gyp doesn't support it yet.
           # Using 3.11 ensures consistency across standard and Alpine builds.
           python-version: '3.11'
 

.github/workflows/build-wasm.yml

@@ -207,6 +207,7 @@ jobs:
           # Use 3.11 to match Alpine 3.19 (Docker builds) which ships Python 3.11.14.
           # Python 3.13 breaks gyp with: TypeError: Strings must be encoded before hashing
           # At: tools/gyp/pylib/gyp/generator/ninja.py:813 hashlib.md5(outputs[0])
+          # Python 3.13 requires .encode() for hashlib, but gyp doesn't support it yet.
           # Using 3.11 ensures consistency across standard and Alpine builds.
           python-version: '3.11'