fix(deps): update rust crate keyring to v3

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
keyring	dependencies	major	2.3.3 -> 3.0.0

---

Release Notes

hwchen/keyring-rs (keyring)

v3.6.3

Compare Source

v3.6.2

Compare Source

• Have docs.rs build docs for all modules on all platforms (thanks to @​unkcpz - see #​235).
• Switch to fastrand for tests (see #​237).

v3.6.1

Compare Source

• Updated dependencies; no code changes.

v3.6.0

Compare Source

• Add combination keystore of keyutils and secret service (thanks to @​soywod).

v3.5.0

Compare Source

• Add debug logging of internal operations (thanks to @​soywod).
• Revert iOS security-framework dependency to v2 (see #​225).

v3.4.0

Compare Source

• Allow use of both secret-service and keyutils.

v3.3.0

Compare Source

• Add support for credential-store attributes other than those used by this crate. This allows the creation of credentials that are more compatible with 3rd-party clients, such as the OS-provided GUIs over credentials.
• Make the textual descriptions of entries consistently follow the form user@service (or user@service:target if a target was specified).

v3.2.1

Compare Source

• Re-enable access to v1 credentials. The fixes of version 3.2 meant that legacy credentials with no target attribute couldn't be accessed.

v3.2.0

Compare Source

• Improve secret-service handling of targets, so that searches on locked items distinguish items with different targets properly.

v3.1.0

Compare Source

• enhance the CLI to allow empty user names and better info about Ambiguous credentials.

v3.0.5

Compare Source

• updated docs and clean up dead code. No code changes.

v3.0.4

Compare Source

• expose a cross-platform module alias via the default module.

v3.0.3

Compare Source

• fix feature linux-native, which was causing compile errors.

v3.0.2

Compare Source

• add missing implementations for iOS set_secret and get_secret

v3.0.1

Compare Source

• add back missing Sync trait on errors.

v3.0.0

Compare Source

• add dbus-secret-service dependency to allow use on *n*x without an async runtime
• (API change) rework feature controls on included keystores: now there is a feature for each keystore, and that keystore is included in a build if and only if its feature is specified and the keystore is supported by the target OS.
• (API change) add direct support for setting and reading binary secret data, not just UTF-8 strings.

---

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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: src-tauri/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path src-tauri/Cargo.toml --package [email protected] --precise 3.6.3
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud