Update node-feature-discovery to v0.16.4

[mzaian]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR update node-feature-discovery to v0.16.4
Update api crds & clusterrole

Does this PR introduce a user-facing change?:

Update node-feature-discovery to v0.16.4

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mzaian

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mzaian]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ant31]

/retest-failed

[ant31]

/ok-to-test

[ant31]

/lgtm

[tico88612]

I think this PR needs a rebase to fix CI.

[tico88612]

/retitle Update node-feature-discovery to v0.16.4

[tico88612]

@mzaian Node Feature Discovery has changes in the readiness and liveness probe detection method, which needs to be fixed.

Kubespray version:

kubespray/roles/kubernetes-apps/node_feature_discovery/templates/nfd-master.yaml.j2

Lines 35 to 49 in 1093c76

	livenessProbe:
	exec:
	command:
	- "/usr/bin/grpc_health_probe"
	- "-addr=:8080"
	initialDelaySeconds: 10
	periodSeconds: 10
	readinessProbe:
	exec:
	command:
	- "/usr/bin/grpc_health_probe"
	- "-addr=:8080"
	initialDelaySeconds: 5
	periodSeconds: 10
	failureThreshold: 10

Node Feature Discovery version: https://github.com/kubernetes-sigs/node-feature-discovery/blob/a851aae9142e44b0df261f3db63cd0fb31c04fdf/deployment/base/master/master-deployment.yaml#L31-L41

[tico88612]

CI passed.

/lgtm