BUG | `useRouteQuery` | Internal state not rolled back when route navigation is cancelled

Describe the bug

When there is a router hook that cancel navigation, internal state is not reset, and there is a mismatch.

It should call .catch() after route navigation, to handle those cases.

Reproduction

Not yet (I'm travelling, I will provide in less than a week)

System Info

System:
    OS: Linux 7.1 Debian GNU/Linux forky/sid
    CPU: (16) x64 AMD Ryzen AI 7 350 w/ Radeon 860M
    Memory: 16.57 GB / 30.53 GB
    Container: Yes
    Shell: 4.7.1 - /usr/bin/fish
  Binaries:
    Node: 20.20.2 - /run/user/1000/fnm_multishells/237912_1789466745919/bin/node
    Yarn: 4.18.0 - /usr/local/bin/yarn
    npm: 10.8.2 - /run/user/1000/fnm_multishells/237912_1789466745919/bin/npm
    bun: 1.3.0 - /home/user/.local/bin/bun
  Browsers:
    Chromium: 152.0.7977.82
    Firefox: 155.0.1
    Firefox Developer Edition: 155.0.1

Used Package Manager

yarn

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a VueUse issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.