fix: let the version resolve when only upstream tags are reachable

[Marius1311]

release.yml is currently red on main — run 33050739790:

ValueError: Error getting the version from source `vcs`:
Can't parse version from tag '1.1.61' (tag_regex='^quadbio-(?P<version>.+)$', tag_prefix='')

#7's tag_regex matched only quadbio-*. But upstream's tags (1.1.61, 1.1.59.post1, …) are
reachable from main, and they are currently the nearest ones — our two release tags were
orphaned by the old force-pushed integration branch. setuptools_scm raises rather than falling
back when the nearest tag doesn't match.

I missed this because I verified the regex in a scratch repo that had only quadbio-* tags.

Two changes:

1. Make the prefix optional — ^(?:quadbio-)?(?P<version>.+)$ — so upstream's tags parse as a
   fallback. Verified against the real repo: resolves to 1.1.62.dev32+g3070196bc.
2. check_wheel.py requires +quadbio. only on release builds. A build off an untagged
   main is a .devN artifact that is never published and has no local segment to carry;
   without this, every push to main would fail the check until the first quadbio-* tag lands.

version	verdict
1.1.61+quadbio.3	accept
1.1.62.dev32+g3070196	accept (dev)
1.1.62.dev1+quadbio.3.gabc	accept
1.1.61.post2	reject — release without our marker

Once quadbio-1.1.61+quadbio.3 is tagged on main it becomes the nearest tag and dev builds
carry the marker too.