## Summary
- Fix `xtasks/release-plz` so `aqua-registry` is rewritten in both
`[dependencies]` and `[build-dependencies]` after the subcrate is
published.
- Avoid Cargo's mixed-source manifest error during release publishing by
removing both local path entries before re-adding the published
crates.io version.

## Root Cause
The release-plz job for `chore: release 2026.5.6 (#9764)` failed at
https://github.com/jdx/mise/actions/runs/25666525627/job/75340319171
after publishing `aqua-registry v2026.5.5`.

The failing step was:

```text
+ cargo add [email protected]
error: failed to parse manifest at `/home/runner/work/mise/mise/Cargo.toml`

Caused by:
  Dependency 'aqua-registry' has different source paths depending on the build target. Each dependency must have a single canonical source path irrespective of build target.
```

PR #9535 introduced the new baked aqua registry pipeline. As part of
that change, the root `mise` crate now depends on `aqua-registry` at
runtime and also in `build.rs`, so `Cargo.toml` has `aqua-registry = {
path = "crates/aqua-registry" }` in both `[dependencies]` and
`[build-dependencies]`.

The release script already handled publishing the subcrate, but it only
ran `cargo add aqua-registry@$AQUA_REGISTRY_VERSION` for the normal
dependency. That made the normal dependency point to crates.io while the
build dependency still pointed at the local workspace path, and Cargo
rejects that mixed source state before the release can continue.

## Test Plan
- `bash -n xtasks/release-plz`
- `mise run lint-fix`
- Manually verified the dependency rewrite sequence: `cargo rm
aqua-registry`, `cargo rm --build aqua-registry`, `cargo add
[email protected]`, `cargo add --build [email protected]`,
then restored the manifest.

*This PR body was generated by an AI coding assistant.*

Made with [Cursor](https://cursor.com)