Remove webhook validation for InfiniBand and RDMA

[e0ne]

Since we always deploy both mutation and validating webhooks there is no need to validate policy for InfiniBand and RDMA enabled because mutating webhook will wet 'isRdma' flag to 'true' for InfiniBand'.

[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 9403579953

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.009%) to 39.664%

---

Totals
Change from base Build 9402838972:	0.009%
Covered Lines:	5175
Relevant Lines:	13047

---

💛 - Coveralls

[SchSeba]

is it bad if we have this validation here? the mutation webhook is coming before the validation webhook so we should be ok here no?

[e0ne]

is it bad if we have this validation here? the mutation webhook is coming before the validation webhook so we should be ok here no?

mutation webhook is always executed before validating, so it means we've got dead code: the statement will be always false

[e0ne]

Here is admission controller documentation: https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#admission-control-phases

[SchSeba]

failing CI lane is not related to this change