[Task]: Integrate r-efi 6.0.0 breaking changes - `unsafe fn` in all function prototypes

[makubacki]

Feature Overview

r-efi v6.0.0 is released. This is a major breaking change that updates function prototypes to be marked unsafe.

This needs to be integrated into Patina.

Solution Overview

This integration was made to better reflect that safety of the code we use so that we can meaningfully and accurately track unsafe code boundaries. Therefore, this should be more than simply passing compilation and linter checks. We should think carefully about the relationships between functions and practical safety concerns, mitigating issues where possible and calling out relevant safety invariants in safety comments.

Alternatives Considered

No response

Urgency

Low

Are you going to implement the feature request?

Someone else needs to implement the feature

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response

[berlin-with0ut-return]

are we planning to split this up as with #583?
the only challenge i can see with this is that we'd have to maintain different versions of r_efi as the unsafe efiapi functions are adopted for different crates., or check in every change at once

[makubacki]

@berlin-with0ut-return, we could go about it in different ways.

My initial though was to make this the main tracking issue, make child issues to split up ownership for individual areas (e.g. you'd take allocators in #1235), and then merge the feature branch back to main when ready.