hack: Add gofmt to update-codegen.sh for consistent code formatting

[akintunero]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This PR adds gofmt -w -s calls after each code generation step in hack/update-codegen.sh to ensure consistent code formatting and simplification of generated Go code.

Why we need it:

• While the script runs goimports, it doesn't run gofmt with the -s flag to simplify code
• This leads to inconsistent formatting of generated code
• Some code generators have added complexity to handle formatting during generation
• Running gofmt ensures all generated code follows Go best practices consistently

What it fixes:

• Addresses the issue where generated code wasn't consistently formatted
• Simplifies generated code using gofmt -s (removes unnecessary complexity)
• Allows code generators to focus on logic rather than formatting concerns
• Ensures consistent code quality across all generated files

Which issue(s) this PR is related to:

Fixes #133609

Special notes for your reviewer:

• This change follows the existing pattern already used in the gen_types_swagger_doc function
• All gofmt calls use -w -s flags for consistent behavior
• The changes are additive and don't modify existing functionality
• Each code generation step now has a corresponding gofmt step for consistency
• This is a low-risk change that improves code quality without breaking existing workflows

Does this PR introduce a user-facing change?

NONE

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

N/A

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR is related to:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

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

[k8s-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[k8s-ci-robot]

Please note that we're already in Test Freeze for the release-1.34 branch. This means every merged PR will be automatically fast-forwarded via the periodic ci-fast-forward job to the release branch of the upcoming v1.34.0 release.

Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Wed Aug 20 02:00:38 UTC 2025.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Needs approval from an approver in each of these files:

• hack/OWNERS

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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: akintunero / name: Olumayowa Akinkuehinmi (74aad7c)

[k8s-ci-robot]

Welcome @akintunero!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines 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.

[k8s-ci-robot]

Hi @akintunero. Thanks for your PR.

I'm waiting for a kubernetes 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.

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.

[BenTheElder]

I think we're still settling on the preferred approach in discussion on the issue

[akintunero]

I think we're still settling on the preferred approach in discussion on the issue

Ok thanks for the update @BenTheElder

[molssongroup]

/easycla