chore(deps): update rust crate tracing-subscriber to v0.3.19

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
tracing-subscriber (source)	dev-dependencies	patch	0.3.18 -> 0.3.19

---

Release Notes

tokio-rs/tracing (tracing-subscriber)

v0.3.19: tracing-subscriber 0.3.19

Compare Source

[ crates.io ] | [ docs.rs ]

This release updates the tracing dependency to v0.1.41 and
the tracing-serde dependency to v0.2.0.

Added

• Add set_span_events to fmt::Subscriber (#​2962)
• tracing: Allow &[u8] to be recorded as event/span field (#​2954)

Changed

• Set log max level when reloading (#​1270)
• Bump MSRV to 1.63 (#​2793)
• Use const thread_locals when possible (#​2838)
• Don't gate with_ansi() on the "ansi" feature (#​3020)
• Updated tracing-serde to 0.2.0 (#​3160)

---

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.

🔕 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: distrans-peer/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path distrans-peer/Cargo.toml --package [email protected] --precise 0.3.19
error: package ID specification `[email protected]` did not match any packages
Did you mean one of these?

  [email protected]