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: (UTC)

• 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 references Guardian.DB.Token.SweeperServer, which was renamed to Guardian.DB.Sweeper in Guardian.DB v3.0, causing a startup failure.
_{Severity: CRITICAL}

Suggested Fix

In lib/cadet/application.ex, update the worker from Guardian.DB.Token.SweeperServer to Guardian.DB.Sweeper to use the correct module name for the new version.

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 application's worker list references
`Guardian.DB.Token.SweeperServer`. Following the upgrade to Guardian.DB v3.0, this
module has been renamed to `Guardian.DB.Sweeper`. This incorrect module reference will
cause the application to fail during initialization because the specified module no
longer exists, preventing the application from starting.

[sentry]

Bug: The upgrade to Guardian.DB v3 is incomplete. It's missing required configuration changes for the adapter and sweeper, which will cause authentication flows to fail at runtime.
_{Severity: CRITICAL}

Suggested Fix

In config/config.exs, add adapter: Guardian.DB.EctoAdapter to the :guardian, Guardian.DB configuration. In lib/cadet/application.ex, update the worker from Guardian.DB.Token.SweeperServer to Guardian.DB.Sweeper. Also, remove the now-obsolete sweep_interval configuration key.

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#L74

Potential issue: Upgrading `guardian_db` to version 3.0 introduces several breaking
changes that are not addressed in this PR. The application configuration is missing the
mandatory `adapter` key, which is required for `Guardian.DB` functions to operate.
Additionally, the token sweeper worker has been renamed from
`Guardian.DB.Token.SweeperServer` to `Guardian.DB.Sweeper`, and the `sweep_interval`
configuration option is obsolete. These omissions will cause runtime failures during
critical authentication operations like token creation, verification, and revocation.

[sentry]

Bug: The guardian_db v3.0.0 upgrade requires an explicit adapter configuration, which is missing. This will cause authentication flows to fail at runtime.
_{Severity: HIGH}

Suggested Fix

In config/config.exs, add adapter: Guardian.DB.EctoAdapter to the :guardian, Guardian.DB configuration block to explicitly use the default Ecto adapter.

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#L74

Potential issue: The upgrade to `guardian_db` v3.0.0 introduces a breaking change where
the adapter must be explicitly configured. The application's configuration in
`config/config.exs` is missing the required `adapter` key. This will cause Guardian.DB
functions, which are used for authentication flows like login and token verification, to
fail at runtime.