Bound runtime dependency ranges and pin build backend

Add version bounds to the runtime dependencies: requests was fully
unbounded and typing-extensions had no upper bound, so a fresh install
could resolve either to any just-published release. As a library,
socketdev declares bounded ranges rather than exact pins - exact pins
in package metadata would conflict with consumers that pin their own
dependencies, including socket-python-cli, which pins its entire
runtime closure (socketsecurity 2.5.10+) and relies on this package's
ranges staying compatible.

Floors match the versions already resolved and tested in uv.lock;
ceilings exclude the next major. Also pins the hatchling build backend
used for sdist builds. Dependabot (uv ecosystem, 7-day cooldown)
already keeps the lockfile fresh within these bounds.

Companion to the socket-python-cli dependency pinning work (CE-359).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: lelia <2418071+lelia@users.noreply.github.com>

Author: lelia

pyproject.toml

@@ -1,14 +1,14 @@
 [build-system]
-requires = ["hatchling"]
+requires = ["hatchling==1.31.0"]
 build-backend = "hatchling.build"
 
 [project]
 name = "socketdev"
 version = "3.4.2"
 requires-python = ">= 3.9"
 dependencies = [
-    'requests',
-    'typing-extensions>=4.12.2'
+    'requests>=2.32.5,<3',
+    'typing-extensions>=4.12.2,<5'
 ]
 readme = "README.rst"
 license = {file = "LICENSE"}

socketdev/version.py

@@ -1 +1 @@
-__version__ = "3.4.2"
+__version__ = "3.4.3"