Multiple tags on same release not handled well

When deploying, `qs` checks that the version details reported by `uv version` agree with those reported by `git tag --points-at HEAD` to ensure that releases are properly version-controlled. Sometimes, though, the same commit will end up with multiple tags, and at that point there's no way the two commands will agree.

A better check would be that the current `uv version` is _among_ the tags that point to the current release.