backport 4.26.0 to jammy

[dann frazier]

[Impact]
This release contains both bug-fixes, new hardware support, and new features for users of Mellanox network controllers. Some examples are:

9bb8d2c8 Fix MaskBootRecordCRC for CX8
3269c0a0 Support GPIO toggling for BF3 same as CX
058537c5 Some CX-7 devices information did not show up when running the query utility mlxfwmanager.
f7534912 [flint][mflash] Support new seventh gen flash for QT3/CX8/BF4

It also addresses:

 * mstflint-dkms in jammy does not build against the 6.5 kernel (bug 2043098)
 * jammy: 4.21.0-7 dropped mstlink binary (bug 2051571)

[Test Case]
The following development and SRU process will be followed:
https://wiki.ubuntu.com/mstflint-Updates

Note: I drafted that to request an SRU special case, but the SRU team decided to approve the backport I was doing at that time (bug 1864475) as a one-off instead of granting a special case.

[Regression Potential]
In order to mitigate the regression potential, the aforementioned testing will be performed. The results of that testing, delineated in the following checklist, will be captured in this bug prior to adding the verification-done tag:

[ ] Verified that all of the utilities from the current version in this series are still present in the new version.
[ ] Verified that the supported flags for each utility in the new version, as described in --help output, are a superset of the existing version in this series.
[ ] The existing version of mstflint upgrades cleanly to the new version.
[ ] Mellanox has executed their mstflint test plan, and results are uploaded to this bug for each series.

[dann frazier (dannf)]

I found that the mstflint command has dropped some command line parameters in 4.26.0 (--private-key-label, --public-key-label, --hsm), so that has more regression potential. For now, I'm moving to Won't Fix.