CA: build images without attestation manifests

[jackfrancis]

What type of PR is this?

What this PR does / why we need it:

From the docker buildx build documentation:

--provenance string Shorthand for "--attest=type=provenance"

This PR sets --provenance=false for cluster-autoscaler docker image builds to allow better ergonomics for including architecture-specific images (e.g., registry.k8s.io/autoscaling/cluster-autoscaler-amd64:v1.34.1) into a cross-arch manifest (e.g., registry.k8s.io/autoscaling/cluster-autoscaler:v1.34.1).

Otherwise we will include attestation manifests data in the resultant image build, and run into errors like this one:

docker manifest create gcr.io/k8s-staging-autoscaling/cluster-autoscaler:v1.30.7 \
      gcr.io/k8s-staging-autoscaling/cluster-autoscaler-amd64:v1.30.7 gcr.io/k8s-staging-autoscaling/cluster-autoscaler-arm64:v1.30.7 gcr.io/k8s-staging-autoscaling/cluster-autoscaler-s390x:v1.30.7
gcr.io/k8s-staging-autoscaling/cluster-autoscaler-amd64:v1.30.7 is a manifest list

Credit to @cpuguy83

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Build images without attestation manifests

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jackfrancis

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:

• cluster-autoscaler/OWNERS [jackfrancis]

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

[jackfrancis]

/release-note-edit

Build images without attestation manifests

[jackfrancis]

/cherry-pick cluster-autoscaler-release-1.34
/cherry-pick cluster-autoscaler-release-1.33
/cherry-pick cluster-autoscaler-release-1.32
/cherry-pick cluster-autoscaler-release-1.31

[k8s-infra-cherrypick-robot]

@jackfrancis: once the present PR merges, I will cherry-pick it on top of cluster-autoscaler-release-1.31, cluster-autoscaler-release-1.32, cluster-autoscaler-release-1.33, cluster-autoscaler-release-1.34 in new PRs and assign them to you.

In response to this:

/cherry-pick cluster-autoscaler-release-1.34
/cherry-pick cluster-autoscaler-release-1.33
/cherry-pick cluster-autoscaler-release-1.32
/cherry-pick cluster-autoscaler-release-1.31

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.