chore: dont check cargo-util semver until 1.86 is released

[weihanglo]

What does this PR try to resolve

This fixes the current confusing failures in our CI pipeline:

• https://github.com/rust-lang/cargo/actions/runs/13465687015/job/37630870984
• https://github.com/rust-lang/cargo/actions/runs/13469881475/job/37642079118?pr=15104

CI job failed because of this major SemVer breakage:

-pub fn strip_prefix_canonical<P: AsRef<Path>>( - path: P, - base: P, +pub fn strip_prefix_canonical( + path: impl AsRef<Path>, + base: impl AsRef<Path>, ) -> Result<PathBuf, std::path::StripPrefixError> {

While cargo-util does have that change violating SemVer,
it is unlikely people use it with turbo-fish syntax.
And cargo-util is essentially for internal use.

See:

• https://rust-lang.zulipchat.com/#narrow/channel/246057-t-cargo/topic/check-version-bump.20failure
• https://forge.rust-lang.org/policies/crate-ownership.html#internal-use

How should we test and review this PR?

CI passes and we're all good, though we are violating SemVer policy 😬.

[rustbot]

r? @ehuss

rustbot has assigned @ehuss.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[ehuss]

Thanks! I would also be fine with just updating the version on beta. But either is fine.