chore(deps): update dependency guardian_db to v3

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
guardian_db (source)	prod	major	~> 2.0 → ~> 3.0

---

Release Notes

ueberauth/guardian_db (guardian_db)

v3.0.0

• Introduced Guardian.DB.Adapter behaviour to allow for custom database adapters to be used with Guardian DB.
  • Add config :guardian, Guardian.DB, adapter: Guardian.DB.EctoAdapter to fall back to the default Ecto adapter.
  • Added Guardian.DB.ETSAdapter.
  • Added Guardian.DB.EctoAdapter.
• Allow migrations mix task with custom table name.
• Make jti and aud required fields, since they are primary keys.

Breaking changes

• Guardian.DB.Token.SweeperServer becomes Guardian.DB.Sweeper
• sweep_interval option is no longer supported. Specify interval directly instead.
• Sweep intervals are now specified in milliseconds instead of minutes.

---

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 is behind base branch, 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: mix.lock

Command failed: install-tool elixir v1.19.5

[sentry]

Bug: The application uses an outdated module name Guardian.DB.Token.SweeperServer and configuration sweep_interval, which were removed in Guardian.DB v3.0, causing a startup failure.
_{Severity: CRITICAL}

Suggested Fix

Update the worker specification in lib/cadet/application.ex to use the new module name, Guardian.DB.Sweeper. Remove the unsupported sweep_interval from config/config.exs and instead pass the interval directly to the Guardian.DB.Sweeper worker, ensuring the value is in milliseconds.

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.exs#L73

Potential issue: The upgrade to Guardian.DB v3.0 introduces breaking changes that have
not been addressed in the application code. The application supervisor attempts to start
a worker using `Guardian.DB.Token.SweeperServer`, but this module was renamed to
`Guardian.DB.Sweeper` in v3.0. This will raise a code loading error during the
`Supervisor.start_link/2` call and cause the application to crash on startup.
Additionally, the `sweep_interval` configuration option is no longer supported and will
be silently ignored; the interval must now be passed directly to the sweeper in
milliseconds.

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