gcb/publish: use E2_HIGHCPU_32 machine type

[Copilot]

cmrel publish --nomock was running very slowly because the publish Cloud Build job used the default (small) machine type instead of a larger one.

• gcb/publish/cloudbuild.yaml: Added machineType: E2_HIGHCPU_32 to the options block, consistent with what gcb/makestage/cloudbuild.yaml already uses.

options:
  # https://cloud.google.com/build/docs/optimize-builds/increase-vcpu-for-builds
  # https://cloud.google.com/build/pricing
  machineType: E2_HIGHCPU_32
  volumes:
  - name: go-modules
    path: /go

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[cert-manager-prow]

Hi @Copilot. Thanks for your PR.

I'm waiting for a cert-manager member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[cert-manager-prow]

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.

📝 Please follow instructions in the contributing guide to update your commits with the DCO

Full details of the Developer Certificate of Origin can be found at developercertificate.org.

The list of commits missing DCO signoff:

• 53a1d69 Initial plan
• 93dbdee Add machineType E2_HIGHCPU_32 to publish cloudbuild.yaml options

Details

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. I understand the commands that are listed here.

[cert-manager-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from maelvls. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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