Build(deps): Bump logger_json from 6.0.3 to 6.2.0

[dependabot]

Bumps logger_json from 6.0.3 to 6.2.0.

Release notes

Sourced from logger_json's releases.

6.2.0

• Added :encoder_opts formatter option which allows passing any options down to Jason encoder, eg. if you want to format the output during development. Thanks to @​anthonator;
• Keep native DateTime, Date and Time structs when encoding them. This prevents those structs from being logged as maps. Thanks to @​imricardoramos;
• Always return :ok even if nothing is logged fixes a bug when plug logger is configured not to return anything. Thanks to @​adamu;
• A new metadata option is added which allows reading configuration from the default logger or any other place in the application environment. The downside of using it is that the application environment will be read on every logged message (since there is no way to init the state of :logger formatter);
• Replace μs with us because unicode is not always available in log aggregators. This value then also will be copied to appropriate provider-specific field. And separately copy it to an appropriate field depending on the formatter used. Thanks to @​bvobart;
• Various docs, typos, and typespec fixes. Thanks to @​dvic, @​moxley.
• Fix Task/GenServer exits correctly in Google Cloud Logger formatter. Thanks @​BrentWheeldon.

Commits

• 17025e0 Make sure GCP/Elastic formatters won't crash on unknown error terms
• f1b0cc9 Improve formatting of the crash reports
• 09b7dc6 Bump version
• 885c731 Properly format HTTP request latency for GCL
• a27b61d Handle Task/GenServer exits correctly in Google formatter (#133)
• 5ad0dee Remap duration_us to spec-compliant fields for Elastic and DataDog formatte...
• 4667ec4 Fix coverage
• 516d588 Bump version
• 625dd08 Replace μs with us because unicode is not always available in log aggregators
• 8ee75eb Allow reading metadata from application environment
• 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
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.