Remove usage of gofuzz

[richardcase]

CAPI (and providers via importing the CAPI package) uses gofuzz for fuzzy testing api conversions via the conversion package.

The gofuzz project has been archived since Jan 2024 so it's not receiving any updates. It's probably worth us considering moving away from using this package to something that is maintained or in-tree.

There is a lot of benefit from fuzzy testing the api conversions so we shouldn't remove these types of tests.

Upstream Kubernetes has marked this as unwanted and suggests randfill be used.

Similar to #9548.

/area testing
/kind cleanup

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[chrischdi]

From the randfill docs

This is a fork of github.com/google/gofuzz, which was archived.

NOTE: This repo is supported only for use within Kubernetes. It is not our intention to support general use. That said, if it works for you, that's great! If you have a problem, please feel free to file an issue, but be aware that it may not be a priority for us to fix it unless it is affecting Kubernetes. PRs are welcome, within reason.

So looks like that's the way to go if the library works for us as a replacement.

[sivchari]

At first glance, we're depending on fuzzing features provided by apimachinery. So if we migrate from gofuzz to randfill, we also remove the apis/meta/fuzzer and apitesting/fuzzer dependecy.