[BUG]:Kernel panic on Intel NUC8 hardware after 9.7→9.8 upgrade — TPM regression (related to #0000440)

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Current Behavior

## Environment
- Hardware: Intel NUC8 (NUC8v5PNH, NUC8v5PNK, NUC8i3BEH, NUC8i3BEK)
- Failing kernel: 5.14.0-687.26.1.el9_8.x86_64 (AlmaLinux 9.8)
- Working kernel: 5.14.0-611.54.3.el9_7.x86_64 (AlmaLinux 9.7)
- Storage: LUKS encrypted root, unlocked via keyfile on EFI partition

## Symptom
System panics at ~1.74 seconds into boot on 9.8 kernel:

[Firmware Bug]: TPM interrupt not working, polling instead
VFS: Unable to mount root fs on unknown-block(0,0)

LUKS root filesystem never mounts. System auto-rolls back to 9.7.
Same hardware boots 9.7 kernel without any issue.

## Root Cause (suspected)
Intel NUC8 uses Intel PTT (firmware TPM, MSFT0101 device via tpm_crb driver).
The 9.8 kernel appears to have regressed TPM initialisation for this device,
similar to the 9.2→9.3 regression documented in bugs.almalinux.org #0000440.

## Impact
Entire fleet of Intel NUC8 call servers cannot upgrade from 9.7.x to 9.8.x.
Workaround: staging ref rolled back to 9.7.12, fleet held on 9.7.

### Expected Behavior

_No response_

### Steps To Reproduce

_No response_

### Anything else?

_No response_

### Search terms

TPM interrupt

No repository files, tests, or entry points are identified. Start by comparing the 5.14.0-687.26.1.el9_8.x86_64 and 5.14.0-611.54.3.el9_7.x86_64 boot behavior on the listed Intel NUC8 models, then review the related TPM regression in bugs.almalinux.org #0000440. Done means identifying the TPM initialization change and confirming a fix or supported workaround restores encrypted-root boot on 9.8.

Written by the indexing model from the issue text.