Update to Jetpack 5.1.4 / L4T 35.6.0

[danielfullmer]

Description of changes

Jetpack 5.1.4 release notes: https://docs.nvidia.com/jetson/archives/jetpack-archived/jetpack-514/release-notes/index.html
L4T 35.6.0 release notes: https://docs.nvidia.com/jetson/archives/r35.6.0/ReleaseNotes/Jetson_Linux_Release_Notes_r35.6.0.pdf

Testing

• Run nix flake check
• Build installer ISO
• Flash all variants
• Boot all variants
• Test UEFI Capsule update (35.3.1 -> 35.5.0)
• Run our (Anduril's) internal automated device tests

[danielfullmer]

Finally merging this update.

Note that the UEFI variable store will be reinitialized after a capsule update to JP5.1.4 due to the new variable authentication feature. A funny (and just sad) consequence of this is that Secure Boot is disabled if it was enabled imperatively through the UEFI menu, instead of declaratively autoenrolling keys through the device tree. See: https://forums.developer.nvidia.com/t/uefi-secure-boot-is-canceled-when-capsule-update-from-r35-4-1-to-r35-6-0/317302

Additionally, this reinitialization also appears to be the reason nvbootctrl dump-slots-info does not report a successful update, as mentioned here. The ESRT variable LastAttemptVersion does not persist across the reboot, so nvbootctrl doesn't think an update actually happened. CC @Princemachiavelli