uv-cache: bump built-wheels cache version

[BurntSushi]

It turns out that #2712 did not fix #2711. After I put up #2712, I
started trying to track down the specific change that caused the
failure. I had assumed at first that it was related to one of our rkyv
types, but it actually ended up being one of our msgpack caches. I think
the failure mode is still fundamentally the same idea: the cached data
changed in a way that is still valid msgpack, but got interpreted
differently after deserializing.

The specific change that caused this was the removal of a field from our
metadata type.

Ideally we would just undo the change and add the field back. But that
change has already been shipped out to users. So I believe the only
plausible choice at this point is to bump the built-wheels cache. This
will unfortunately mean that uv will need to re-build wheels.

Fixes #2711

[BurntSushi]

Here is my test protocol. First, the failure:

$ rm -rf ~/.cache/uv && rm -rf .venv && uv-0.1.24 venv && uv-0.1.24 pip install -q homeassistant
Using Python 3.12.0 interpreter at: /home/andrew/.pyenv/versions/3.12.0/bin/python3
Creating virtualenv at: .venv
Activate with: source .venv/bin/activate
$ uv-0.1.25 pip install -q homeassistant --reinstall-package homeassistant
error: Failed to download and build: pyric==0.1.6.3
  Caused by: Failed to deserialize cache entry
  Caused by: expected version to start with a number, but no leading ASCII digits were found
$

And now a demonstration that this PR doesn't have the issue:

$ rm -rf ~/.cache/uv && rm -rf .venv && uv-0.1.24 venv && uv-0.1.24 pip install -q homeassistant
Using Python 3.12.0 interpreter at: /home/andrew/.pyenv/versions/3.12.0/bin/python3
Creating virtualenv at: .venv
Activate with: source .venv/bin/activate
$ uv-this-pr pip install -q homeassistant --reinstall-package homeassistant
$

[charliermarsh]

You should also be able to un-bump the simple cache version.

[charliermarsh]

But... I don't feel strongly. Let's just leave it bumped actually.

[BurntSushi]

Yeah I thought about that, but didn't want to get too cute since that bump already landed on main.