Check for kernel lockdown only in mlx plugin

[SchSeba]

We need to check for the kernel lockdown only in the mlx plugin.

if the firmware in the mlx card is already configured as needed we can allocate virtual functions even if the system is in lockdown

[github-actions[bot]]

Thanks for your PR, To run vendors CIs use one of:

• /test-all: To run all tests for all vendors.
• /test-e2e-all: To run all E2E tests for all vendors.

• /test-e2e-nvidia-all: To run all E2E tests for NVIDIA vendor.

  To skip the vendors CIs use one of:

• /skip-all: To skip all tests for all vendors.
• /skip-e2e-all: To skip all E2E tests for all vendors.
• /skip-e2e-nvidia-all: To skip all E2E tests for NVIDIA vendor. Best regards.

[coveralls]

Pull Request Test Coverage Report for Build 8506776095

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 10 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.02%) to 38.324%

---

Files with Coverage Reduction	New Missed Lines	%
pkg/host/mock/mock_host.go	10	31.44%
<!--	Total:	10		-->

Totals
Change from base Build 8467233545:	-0.02%
Covered Lines:	4794
Relevant Lines:	12509

---

💛 - Coveralls

[SchSeba]

@e0ne @ykulazhenkov please take a look this can be a way to make the sriov-operator work with mlx cards in secure mode.

in general the idea is

1. the user configure the max number of vfs he wants in the firmware as part of the installation process (not secure boot)
2. switch the system to secure boot
3. install the operator with disablePlugin option for mlx
4. create the sriovNetworkNodePolicy as always