chore(deps): bump ecto from 3.12.6 to 3.13.1

[dependabot]

Bumps ecto from 3.12.6 to 3.13.1.

Changelog

Sourced from ecto's changelog.

v3.13.1 (2025-06-19)

Bug fixes

• [Ecto.Repo] Do not automatically apply HOT updates on upsert with replace. It is the user responsibility to make sure they do not overlap

v3.13.0 (2025-06-18)

Requires Elixir v1.14+.

Enhancements

• [Ecto] Support Elixir's built-in JSON
• [Ecto.Enum] Add Ecto.Enum.cast_value/3
• [Ecto.Query] Allow schema to be used for values list types
• [Ecto.Query] Allow strings in field/2
• [Ecto.Query] Add identifier/1 in queries
• [Ecto.Query] Add constant/1 in queries
• [Ecto.Query] Allow exclude/2 to remove windows
• [Ecto.Query] Allow source fields in json_extract_path
• [Ecto.Repo] Add Ecto.Repo.prepare_transaction/2 user callback
• [Ecto.Repo] Add Ecto.Repo.all_by/3
• [Ecto.Repo] Add Ecto.Repo.transact/2
• [Ecto.Repo] Allow HOT updates on upsert queries in Postgres by removing duplicate fields during replace_all_except
• [Ecto.Schema] Support @schema_redact: :all_except_primary_keys module attribute

Bug fixes

• [Ecto.Query] Allow select merging maps with all nil values
• [Ecto.Query] map/2 in queries now always returns a map on joins, even on left joins, for consistency with from sources
• [Ecto.Schema] Fix an issue where Ecto could warn an association did not exist, when it did

Soft deprecations (no warnings emitted)

• [Ecto.Repo] Ecto.Repo.transaction/2 is soft-deprecated in favor of Ecto.Repo.transact/1
• [Ecto.Query.API] literal/1 is deprecated in favor of identifier/1

Commits

• d26c3f0 Release v3.13.1
• 9742434 Do not apply HOT optimization on :replace
• d3d5193 Update CHANGELOG.md
• e51222e Update CHANGELOG.md
• 896dcfa Update CHANGELOG.md
• 5034849 Update CHANGELOG
• 8fbf588 Release v3.13.0
• abc1624 Update docs, remove Multi guide (#4619)
• be60b77 HOT optimization for upserts with :replace and :replace_all_except (#4617)
• c87024c Add Repo.transact/2 and soft-deprecate transaction/2 (#4618)
• 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)