Cherry-pick pwr-mlxbf commits from linux-next

[Asmaa Mnebhi]

SRU Justification:

[Impact]

Cherry pick pwr-mlxbf patches from linux-next.

[Fix]

* Revert existing pwr-mlxbf driver changes
* Cherry-pick all the following commits from linux-next:
  a4c0094fcf7628f31bf82a7b25e7f51ee5a22324
  a5a3d94fc4edecb894bc79810aea511ff9261c09
  a578cc3af5cea5c7a912d2cfb8601875eb8ce451
  926ce6ba25101ccc659475e01ce5748374ab5856
  b9afaa069e58939d95923c27c2fd76a0523119a7
  292fe42c34a9e9eea07f58a691813e077e9ca86f

[Test Case]

* All test cases are for BF3 only
* Check that the pwr-mlxbf driver gets loaded at boot time without issues
* rmmod and modprobe driver without errors
* Test driver by issuing graceful reboot from the BMC via ipmitool command.

[Regression Potential]

* Make sure all existing pwr-mlxbf functionality is still the same (see tests above).

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

This bug is awaiting verification that the linux-bluefield/5.15.0-1067.69 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!