Rust Dependency: Update patina requirement from 22 to 23

[dependabot]

Updates the requirements on patina to permit the latest version.

Release notes

Sourced from patina's releases.

patina-v23.3.0

What's Changed

This is a cherry-pick of #1767 from major branch into main. It was determined that this was not a breaking change and is needed in main. Please refer to the documentation in #1767 for this change - however the How This Was Tested and Integration Instrucitons have been updated accordingly, as platforms should re-run the patina-dxe-readiness-tool v0.4.0 or greater.

• Impacts functionality?
• Impacts security?
• Breaking change?
• Includes tests?
• Includes documentation?

How This Was Tested

Platforms should re-run the patina-readiness-tool v0.4.0 or greater when about to ingest this change. They should confirm that FV HOBs are covered by memory allocation HOBs. If not, page aligned memory allocation HOBs must be produced by the platform for the FV regions.

Separately, the platform should identify if any non-page aligned GCD allocations are being made (debug_asserts will catch this). If so, they must convert them to page aligned allocations. This does not affect AllocatePool allocations, only direct GCD allocations through AllocateMemorySpace().

Integration Instructions

Platforms should re-run the patina-readiness-tool v0.4.0 or greater when about to ingest this change. They should confirm that FV HOBs are covered by memory allocation HOBs. If not, page aligned memory allocation HOBs must be produced by the platform for the FV regions.

Separately, the platform should identify if any non-page aligned GCD allocations are being made (debug_asserts will catch this). If so, they must convert them to page aligned allocations. This does not affect AllocatePool allocations, only direct GCD allocations through AllocateMemorySpace().

  </blockquote>
  <hr>
</details>

spin_locked_gcd.rs has grown to >7k lines. Split it up, w/o any functional change into a few modules:

... (truncated)

Commits

• 8561bc1 Chore: Update crate versions to 23.3.0
• 773f333 GCD: Do Not Allocate FV HOB Regions
• f34b7d2 GCD: Enforce Page Aligned Allocations
• 22cfdb4 Revert "dxe: GCD: Don't Assert on Non-Page Aligned GCD Allocations"
• 5ebcca0 GCD: Fix is_efi_memory_map_descriptor Length Check
• d5f80ab README.md: Add Patina OS boot badges (#1800)
• e751bc1 GCD: Reorganize spin_locked_gcd.rs
• 0abda1c Chore: Update crate versions to 23.2.1
• 6c35b72 Flush TLB at EL1 using tbli vmalle1 (#1794)
• 79dae65 DXE Core: Add Platform Registered VE Handler Support
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[Michael Kubacki (makubacki)]

Closing as the complete set of changes needed were already merged to release/202608 in f661444.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.