fix(deps): update tokio-tracing monorepo

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
tracing (source)	dependencies	patch	0.1.41 -> 0.1.43
tracing (source)	workspace.dependencies	patch	0.1.41 -> 0.1.43
tracing-subscriber (source)	dependencies	patch	0.3.3 -> 0.3.22
tracing-subscriber (source)	dependencies	patch	0.3.20 -> 0.3.22
tracing-subscriber (source)	workspace.dependencies	minor	0.2.18 -> 0.3.0

---

Release Notes

tokio-rs/tracing (tracing)

v0.1.43: tracing 0.1.43

Compare Source

Important

The previous release 0.1.42 was yanked because #​3382 was a breaking change.
See further details in #​3424. This release contains all the changes from that
version, plus a revert for the problematic part of the breaking PR.

Fixed

• Revert "make valueset macro sanitary" (#​3425)

v0.1.42: tracing 0.1.42

Compare Source

Important

The Span::record_all method has been removed from the documented API. It
was always unsuable via the documented API as it requried a ValueSet which
has no publically documented constructors. The method remains, but should not
be used outside of tracing macros.

Added

• attributes: Support constant expressions as instrument field names (#​3158)
• Add record_all! macro for recording multiple values in one call (#​3227)
• core: Improve code generation at trace points significantly (#​3398)

Changed

• tracing-core: updated to 0.1.35 (#​3414)
• tracing-attributes: updated to 0.1.31 (#​3417)

Fixed

• Fix "name / parent" variant of event! (#​2983)
• Remove 'r#' prefix from raw identifiers in field names (#​3130)
• Fix perf regression when release_max_level_* not set (#​3373)
• Use imported instead of fully qualified path (#​3374)
• Make valueset macro sanitary (#​3382)

Documented

• core: Add missing dyn keyword in Visit documentation code sample (#​3387)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[red-hat-konflux]

⚠️ Artifact update problem

Renovate failed to update artifacts 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: src/agent/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path src/agent/Cargo.toml --workspace
info: syncing channel updates for '1.85.1-x86_64-unknown-linux-gnu'
info: latest update on 2025-03-18, rust version 1.85.1 (4eb161250 2025-03-15)
info: downloading component 'cargo'
error: component download failed for cargo-x86_64-unknown-linux-gnu: error opening file for download: cleaning up cached downloads: No such file or directory (os error 2)

File name: src/dragonball/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path src/dragonball/Cargo.toml --workspace
info: syncing channel updates for '1.85.1-x86_64-unknown-linux-gnu'
info: latest update on 2025-03-18, rust version 1.85.1 (4eb161250 2025-03-15)
info: downloading component 'cargo'
error: component download failed for cargo-x86_64-unknown-linux-gnu: error opening file for download: cleaning up cached downloads: No such file or directory (os error 2)

File name: src/runtime-rs/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path src/runtime-rs/Cargo.toml --workspace
info: syncing channel updates for '1.85.1-x86_64-unknown-linux-gnu'
info: latest update on 2025-03-18, rust version 1.85.1 (4eb161250 2025-03-15)
info: downloading component 'cargo'
error: component download failed for cargo-x86_64-unknown-linux-gnu: error opening file for download: cleaning up cached downloads: No such file or directory (os error 2)

File name: src/runtime-rs/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path src/runtime-rs/crates/runtimes/Cargo.toml --workspace
info: syncing channel updates for '1.85.1-x86_64-unknown-linux-gnu'
info: latest update on 2025-03-18, rust version 1.85.1 (4eb161250 2025-03-15)
info: downloading component 'cargo'
error: component download failed for cargo-x86_64-unknown-linux-gnu: error opening file for download: cleaning up cached downloads: No such file or directory (os error 2)

File name: src/tools/trace-forwarder/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path src/tools/trace-forwarder/Cargo.toml --workspace
info: syncing channel updates for '1.85.1-x86_64-unknown-linux-gnu'
info: latest update on 2025-03-18, rust version 1.85.1 (4eb161250 2025-03-15)
info: downloading component 'cargo'
error: component download failed for cargo-x86_64-unknown-linux-gnu: error opening file for download: cleaning up cached downloads: No such file or directory (os error 2)

[littlejawa]

/hold