Bump CSI spec 1.10

[jsafrane]

What type of PR is this?
/kind cleanup

What this PR does / why we need it:

Bump CSI spec to 1.10.0 and csi-test to 5.3.0.

• gomock is not able to match newly generated Protobuf messages from csi-test, because their private fields differ. Implement a custom message matcher.
• k8s.io/apimachinery can be used to compare API objects, but it panics on the new protobuf messages. Use a generic cmp.Equal instead, as suggested in https://protobuf.dev/reference/go/faq/#deepequal

WIP:

• the matcher should be probably in csi-tests repo, as it's going to be used by many sidecars.

Updated CSI spec to 1.10.0

cc @AndrewSirenko @xing-yang @gnufied

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane

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 [jsafrane]

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

[jsafrane]

I filed an issue in the CSI spec repo: container-storage-interface/spec#570
This should not be a minor package bump.

[AndrewSirenko]

This fixes tests for external-health-monitor and liveness probe when moved to csi-test

• Add Protobuf Matcher utility csi-test#553

See tests passing with replaced csi-test module:

• WIP: Bump csi-spec to v1.10.0 livenessprobe#296
• WIP: Upgrade CSI-Spec to v1.10.0 external-health-monitor#277

I can raise a PR on your fork for this provisioner PR, changing Protobuf -> csitestutil.Protobuf once we release new version of csi-test.

[jsafrane]

@AndrewSirenko I updated to csi-test 5.3.1, PTAL