chore(deps): update rust crate base64 to 0.22.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
base64	workspace.dependencies	minor	0.21.7 -> 0.22.0

---

Release Notes

marshallpierce/rust-base64 (base64)

v0.22.0

Compare Source

• DecodeSliceError::OutputSliceTooSmall is now conservative rather than precise. That is, the error will only occur if the decoded output cannot fit, meaning that Engine::decode_slice can now be used with exactly-sized output slices. As part of this, Engine::internal_decode now returns DecodeSliceError instead of DecodeError, but that is not expected to affect any external callers.
• DecodeError::InvalidLength now refers specifically to the number of valid symbols being invalid (i.e. len % 4 == 1), rather than just the number of input bytes. This avoids confusing scenarios when based on interpretation you could make a case for either InvalidLength or InvalidByte being appropriate.
• Decoding is somewhat faster (5-10%)

---

Configuration

📅 Schedule: Branch creation - "before 5am on the first day of the month" (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 has been generated by Mend Renovate. View repository job log here.

[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: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package base64@0.21.7 --precise 0.22.0
    Updating crates.io index
error: failed to select a version for the requirement `base64 = "^0.21.0"`
candidate versions found which didn't match: 0.22.0
location searched: crates.io index
required by package `gix-transport v0.41.2`
    ... which satisfies dependency `gix-transport = "^0.41.2"` (locked to 0.41.2) of package `gix v0.61.0`
    ... which satisfies dependency `gix = "^0.61.0"` (locked to 0.61.0) of package `cargo v0.80.0 (/tmp/renovate/repos/github/rust-lang/cargo)`
    ... which satisfies path dependency `cargo` (locked to 0.80.0) of package `benchsuite v0.0.0 (/tmp/renovate/repos/github/rust-lang/cargo/benches/benchsuite)`
perhaps a crate was updated and forgotten to be re-vendored?

[rustbot]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @weihanglo (or someone else) some time within the next two weeks.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

[epage]

@bors r+

[bors]

📌 Commit aedc6c7 has been approved by epage

It is now in the queue for this repository.

[bors]

⌛ Testing commit aedc6c7 with merge f4ea1d1...

[bors]

☀️ Test successful - checks-actions
Approved by: epage
Pushing f4ea1d1 to master...