Rebase dasharo/coreboot to 25.09

[miczyg1]

Create a new branch, starting from 25.09 release, applying our unmerged commits on top of that. Before the rebase will start, the upstream coreboot 25.12 release might be out already. Pick the newest version, if that happens.

In the process we might try to squash some related commits - in that case, we should leave some notes there, or in commit message (or both).

We can use this issue as a general discussion of this process.

As for branch naming and the flow, follow: https://docs.dasharo.com/dev-proc/source-code-structure/#rebase-process
Additional tasks, that must be done during rebase:

• After all commits from Dasharo fork are applied we also need to cherry-pick all work made for AMD Turin: https://review.coreboot.org/q/topic:turin_poc+-status:abandoned

• Patches classification - inspired by: https://docs.yoctoproject.org/contributor-guide/recipe-style-guide.html#patch-upstream-status
  Add Upstream-Status tag to indicate whether the patch is Pending (to be submitted upstream), or Inappropriate [dasharo-specific] (not planned to upstream), or something else

[pietrushnic]

https://github.com/coreboot/coreboot/tree/25.12