Add sonobouy conformance to the build pipeline

[displague]

• [ ] Run the conformance testing
• [ ] Identify any open issues
• [ ] Automate running the conformance testing

https://github.com/aws-samples/eks-anywhere-addons

/cc @elamaran11

[elamaran11]

Hi @displague We did run our Conformance Framework on an EKSA Baremetal environment with Equinix metal and following are our inferences.

1. Sonobuoy run failed with two errors on the environment and below is a snapshot of the failure and run :

Summarizing 2 Failures:

[Fail] [sig-scheduling] SchedulerPredicates [Serial] [It] validates that NodeSelector is respected if not matching  [Conformance]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/scheduling/predicates.go:436

[Fail] [sig-apps] Daemon set [Serial] [It] should rollback without unnecessary restarts [Conformance]
/workspace/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:432

Ran 346 of 7044 Specs in 6271.183 seconds
FAIL! -- 344 Passed | 2 Failed | 0 Pending | 6698 Skipped

2. We want to know what storage driver configurations is supported by Equinix to stateful workloads. Was this validated with any CSI drivers. We tried to use LocalEBS and we couldnt get an ISV addon installed because of iSCSI dependency on bottlerocket nodes. We do have a bottlerocket issue in GitHub for iSCSI support with our service team but i want to bring this aspect and check on if Stateful workloads was validated EKSA with BottleRocket BM Cluster.

Please let me know if you have any questions or comments on this.

[displague]

Related https://github.com/aws/eks-anywhere/issues/3423