deps: Bump Cargo.lock version

[kurosakishigure]

Description

• Bump Cargo.lock version
• What is the purpose of this PR?
  • Bump Cargo.lock version
• What problem does it solve?
  • None
• Are there any breaking changes or backwards compatibility issues?
  • None

Related Issue

None.

Type of Change

• Other (please describe): Deps

How Has This Been Tested?

• I have run unit tests
• I have tested the changes manually
• I have tested in a staging environment

Checklist

• My code follows the coding style guidelines of this project
• I have written or updated relevant documentation (if applicable)
• I have added or updated tests to cover my changes (if applicable)
• All new and existing tests pass
• I have reviewed my code for any potential issues
• Link the relevant issue to this PR (if applicable)
• Add labels to this PR
• I have read and followed the guidelines in CONTRIBUTING.md

Additional Notes

This is a special PR, and I believe it will only be needed this once.
Its purpose is to resolve a version synchronization issue caused by the initial commit conflicting with subsequent bot updates to dependencies.
I’ve manually forced everything to sync now, so everything is up-to-date—hopefully, it stays that way! :)

After this PR, the bot shouldn’t cause any more of these “weird” desync issues between Cargo.toml and Cargo.lock🤔.