v0.1.0a2

The published image was missing both optional extras, and the docs promised both

Found by running the artefact rather than reading the source. The Dockerfile's ARG EXTRAS=
is empty and the release workflow passed no --build-arg, so 0.1.0a1 shipped without
sentry-sdk and without psycopg:

• with HULLWORK_ERROR_DSN set the container exits 3, telling you to run a pip install
  nobody can run against an image they pulled — a capability the FAQ, docs/status.md and the
  deployment notes all describe;
• a postgresql+psycopg:// URL died as ModuleNotFoundError: No module named 'psycopg' in a
  raw SQLAlchemy traceback, while the support matrix says Postgres works.

Nobody noticed because a development checkout installs [dev], which carries both. The defect
was only reachable through the artefact.

The release now builds with [postgres,telemetry], and a test asserts both by name so a later
edit cannot drop one silently the way their absence was never noticed.

And the case that survives the fix — building your own image without the extra — gets a
sentence instead of the traceback: which extra carries the driver, and that SQLite needs
nothing. By asking the dialect rather than matching the URL against drivers we recognise, so a
driver nobody here thought of is refused the same way.

Version 0.1.0a2, because the fix lives in the build and only a release can carry it.