Cap dqlite-wire pin below 0.2.0 to block silent major-bump install

The cross-package pin was an unbounded ``>=0.1.3``. The four packages
in the dqlite stack are co-developed, share private import surfaces
(see XP1 for one example), and have never been validated against any
combination other than the released-together set. Allowing
``pip install -U dqlite-wire`` to fetch a 0.2.0 (which can carry
breaking refactors of the private surface) silently would break
``import dqliteclient`` at first use.

Mirror the SA-side ``sqlalchemy>=2.0,<3.0`` pattern: add the
explicit ``<0.2.0`` upper bound. The same upper-bound discipline
lands on dbapi → client and sqlalchemy-dqlite → dbapi.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: antoineleclair

pyproject.toml

@@ -23,7 +23,7 @@ classifiers = [
     "Topic :: Database :: Database Engines/Servers",
     "Typing :: Typed",
 ]
-dependencies = ["dqlite-wire>=0.1.3"]
+dependencies = ["dqlite-wire>=0.1.3,<0.2.0"]
 
 [tool.uv.sources]
 dqlite-wire = { path = "../python-dqlite-wire", editable = true }