mlxbf-bootctl: fails to report info about cards using dev keys

[David Thompson]

SRU Justification:

[Impact]

There is a gap in the mlxbf-bootctl driver logic, resulting in failure to
report when a secure boot enabled card is using development keys. The program
will instead report lifecycle state as "GA Secured" which is misleading.

[Fix]

Bring in the following upstream commit from linux-next:
  "mlxbf-bootctl: correctly identify secure boot with development keys"

[Test Case]

Enable secure boot on a BF3 card that is using development keys
Login as root on BF3
Run the command "mlxbf-bootctl"
Verify that the "lifecycle state" row shows "Secured (development)"

[Regression Potential]

Low risk change, cherry pick of upstream approved commit

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is awaiting verification that the linux-bluefield/5.15.0-1034.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-done-jammy-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-jammy-linux-bluefield' to 'verification-failed-jammy-linux-bluefield'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!