fix(void): carry python3-pysocks and constrain the audio and SOCKS floors

Void's stock python3-PyAudio (0.2.12_5) and python3-pysocks (1.7.0_8) sit
below the project floors (pyaudio>=0.2.13, PySocks>=1.7.1). voculinux
depended on both by bare name, which an installed stock package already
satisfies, so a user who had the stock packages was never upgraded.

- add packaging/void/srcpkgs/python3-pysocks: PySocks 1.7.1 from the PyPI
  sdist that uv.lock pins (sha256 3f8804571ebe159c380ac6de37643bb4685970655d3bba243530d6558b799aa0)
- voculinux depends on python3-PyAudio>=0.2.14_1 and python3-pysocks>=1.7.1_1
- the install smoke installs the stock packages first, then voculinux, and
  fails unless each reads back as its carried pkgver
- tests: each constraint must name its carried template's current version
  and revision; the stock version must sit below the floor; the depends
  parser refuses malformed tokens instead of stripping them
- docs: "Version floors" in packaging/void/README.md; a pointer in
  docs/RELEASE_PROCESS.md

Refs #16

docs/RELEASE_PROCESS.md

@@ -57,6 +57,14 @@ is not `repository-key.plist`. The private key is never committed; only the
 public `.plist` is. Key generation and the check that a private key matches the
 committed public key are in `packaging/void/README.md`.
 
+The carried Void templates in `packaging/void/srcpkgs/` track the project's own
+pins. `python3-PyAudio` and `python3-pysocks` replace stock Void packages below
+the floors in `pyproject.toml`, and `voculinux` depends on each with a `>=`
+constraint. When a floor or a carried version changes, change the template and
+its constraint in the same pull request: the offline tests in
+`tests/test_void_small_deps.py` and `tests/test_void_app_template.py` fail
+until they agree. The reasoning is in `packaging/void/README.md`, "Version floors".
+
 ## Quick Release Checklist
 
 Use this checklist for every release: