🐛 fix(cli): format version subcommand output

[vitorfloriano]

This PR changes the version subcommand output to a human-readable table format:

• Current:

$ kubebuilder version
Version: cmd.version{KubeBuilderVersion:"v4.10.1", KubernetesVendor:"1.34.1", GitCommit:"$Format:%H$", BuildDate:"1970-01-01T00:00:00Z", GoOs:"unknown", GoArch:"unknown"}

• After:

$ kubebuilder version
KubeBuilder:        (devel)
Kubernetes Vendor:  1.34.1
Git Commit:         c7b5b17b8e1dc4f0fdaf0910464a4d44000365bf
Build Date:         2025-12-24T01:25:15Z
Go OS/Arch:         linux/amd64

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vitorfloriano
Once this PR has been reviewed and has the lgtm label, please assign kavinjsir for approval. 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

[k8s-ci-robot]

Hi @vitorfloriano. Thanks for your PR.

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

[vitorfloriano]

Hi @camilamacedo86 hope you're doing well.

I opened helm/helm#31574 to fix a similar issue and was informed by the Helm maintainers that formating the version subcommand output would be considered a breaking change, so I would like to know if that could be the case for Kubebuilder as well.

I'm not sure if any other programs are consuming the output from version.

[camilamacedo86]

Hi @camilamacedo86 hope you're doing well.

I opened helm/helm#31574 to fix a similar issue and was informed by the Helm maintainers that formating the version subcommand output would be considered a breaking change, so I would like to know if that could be the case for Kubebuilder as well.

I'm not sure if any other programs are consuming the output from version.

Thanks for working on this — the new output is much nicer for humans 👍
Yes, this can still be a breaking change in practice if some users are grepping or parsing the current output (even if they shouldn’t). Right now there’s no compatibility or machine-readable option.

I think we can move forward if we add a minimal stable output format, for example:

kubebuilder version -o json
# or
kubebuilder version --output=json

and keep the pretty output as the default. This gives tooling a stable contract while improving the human UX.