fix(deps): update rust crate tikv-jemalloc-ctl to 0.6.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
tikv-jemalloc-ctl	dependencies	minor	0.5.4 -> 0.6.0

---

Release Notes

tikv/jemallocator (tikv-jemalloc-ctl)

v0.6.0

• Fix build on riscv64gc-unknown-linux-musl (#​67) (#​75)
• Allow jemalloc-sys to be the default allocator on musl linux (#​70)
• Add Chimera Linux to gmake targets (#​73)
• Add profiling options to jemalloc-ctl (#​74)
• Fix jemalloc version not shown in API (#​77)
• Fix jemalloc stats is still enabled when stats feature is disabled (#​82)
• Fix duplicated symbol when build and link on aarch64-linux-android (#​83)
• Revise CI runner platform on macOS (#​86)
• Allow setting per-target env (#​91)
• Remove outdated clippy allows (#​94)
• Set MSRV to 1.71.0 (#​95)

Note since 0.6.0, if you want to use jemalloc stats, you have to enable the
feature explicitly.

---

Configuration

📅 Schedule: Branch creation - "* 0-4,22-23 * * 1-5,* * * * 0,6" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --workspace
    Updating crates.io index
    Updating git repository `https://github.com/kubewarden/policy-evaluator`
From https://github.com/kubewarden/policy-evaluator
 * [new ref]         327b8a6773b8bf43f20e686722b4517067a3bff6 -> refs/commit/327b8a6773b8bf43f20e686722b4517067a3bff6
    Updating git repository `https://github.com/kubewarden/policy-fetcher`
From https://github.com/kubewarden/policy-fetcher
 * [new ref]         c031bb4126c8be24f8f8c3e1dfe122291e4b7989 -> refs/commit/c031bb4126c8be24f8f8c3e1dfe122291e4b7989
error: failed to select a version for `tikv-jemalloc-sys`.
    ... required by package `tikv-jemallocator v0.5.4`
    ... which satisfies dependency `tikv-jemallocator = "^0.5.4"` of package `policy-server v1.20.0 (/tmp/renovate/repos/github/kubewarden/policy-server)`
versions that meet the requirements `^0.5.0` are: 0.5.4+5.3.0-patched, 0.5.3+5.3.0-patched, 0.5.2+5.3.0-patched, 0.5.1+5.3.0-patched, 0.5.0+5.3.0

the package `tikv-jemalloc-sys` links to the native library `jemalloc`, but it conflicts with a previous package which links to `jemalloc` as well:
package `tikv-jemalloc-sys v0.6.0+5.3.0-1-ge13ca993e8ccb9ba9847cc330696e02839f328f7`
    ... which satisfies dependency `tikv-jemalloc-sys = "^0.6.0"` of package `tikv-jemalloc-ctl v0.6.0`
    ... which satisfies dependency `tikv-jemalloc-ctl = "^0.6.0"` of package `policy-server v1.20.0 (/tmp/renovate/repos/github/kubewarden/policy-server)`
Only one package in the dependency graph may specify the same links value. This helps ensure that only one copy of a native library is linked in the final binary. Try to adjust your dependencies so that only one package uses the `links = "jemalloc"` value. For more information, see https://doc.rust-lang.org/cargo/reference/resolver.html#links.

failed to select a version for `tikv-jemalloc-sys` which could resolve this conflict

[jvanz]

Closing this PR because all the jemalloc crates should be updated together.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (0.6.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.