Bump tracing from 0.1.21 to 0.1.22

[dependabot[bot]]

Bumps tracing from 0.1.21 to 0.1.22.

Commits

• fc3eb9f tracing: prepare to release v0.1.22 (#1119)
• 43440ef chore(deps): update pin-project-lite requirement from 0.1 to 0.2 (#1116)
• 75ba278 ci: switch to audit-check GitHub Action for cargo audit (#1117)
• 50e1fad ci: install cargo-hack from GitHub release instead of using cache (#1100)
• 1cdd554 opentelemetry: prepare for 0.9.0 release (#1104) (#1105)
• 642ad19 opentelemetry: update to latest otel release version (#1049) (#1099)
• 692c56f subscriber: prepare to release 0.2.15 (#1083)
• 2d27703 subscriber: fix accessing the field formatter from FmtContext (#1081) (#1082)
• 8bdc6c3 subscriber: add Pretty formatter (backports #1067) (#1080)
• 3bc2fd3 subscriber: prepare to release 0.2.14 (#1065)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually

[mergify[bot]]

bors r+

[bors[bot]]

Build succeeded:

• build (x86_64-unknown-linux-gnu)
• build (x86_64-pc-windows-gnu)
• static_analysis
• build (x86_64-apple-darwin)
• build (armv7-unknown-linux-gnueabihf)