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

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

CI job failed because of this major SemVer breakage:

```diff
-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

Author: weihanglo

crates/xtask-bump-check/src/xtask.rs

@@ -132,6 +132,16 @@ fn bump_check(args: &clap::ArgMatches, gctx: &cargo::util::GlobalContext) -> Car
         // as the publish of these crates are not tied with Rust release process.
         // See `TO_PUBLISH` in publish.py.
         "home",
+        // Don't check this util 1.86 is released.
+        // While it does have a SemVer breakage,
+        // 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
+        "cargo-util",
     ];
 
     status(&format!("base commit `{}`", base_commit.id()))?;