chore(deps): Refresh mix.lock files

[sentry-release-bot]

Automated weekly refresh of the committed mix.lock files (including the per-Elixir-version-range lockfiles) via mix deps.update --all, keeping dependency pins current with the latest security patches allowed by each project's version constraints.

#skip-changelog

Action required

• If CI passes on this PR, it's safe to approve and merge.
• If CI fails, a dependency update broke something — investigate before merging.

🤖 Automatically created by .github/workflows/update_lockfiles.yml.

[sentry]

Bug: The major version upgrade of hackney to 4.6.0 introduces a breaking change. The call to :hackney_pool.child_spec/2 in Sentry.HackneyClient will likely fail, causing application startup crashes.
_{Severity: CRITICAL}

Suggested Fix

The Sentry.HackneyClient implementation should be updated to be compatible with the new pooling API in hackney 4.x. Before merging, verify the correct way to start a supervised connection pool in the new version and adjust the child_spec function accordingly. Alternatively, pin the hackney dependency to a compatible ~> 1.20 version to prevent this breaking change until the client can be updated.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: mix.lock#L32

Potential issue: The `hackney` dependency is being upgraded from version 1.20.1 to
4.6.0, which is a major rewrite. The default HTTP client, `Sentry.HackneyClient`,
directly calls `:hackney_pool.child_spec/2` to start its connection pool. This
function's API has likely changed or been removed in the new version of `hackney`. As a
result, when `Sentry.Application` attempts to start the client, the call will fail,
causing a runtime crash. This will prevent any application using the default Sentry
configuration with Hackney from starting successfully. The existing code guard only
checks if the `:hackney_pool` module is loaded, not if the function signature is valid.

Also affects:

• mix-1.18.lock:32~32
• mix-1.15-1.17.lock:32~32

_{Did we get this right? 👍 / 👎 to inform future reviews.}