feat: add kind env command

[ANISHSAJIKUMAR]

Add a new kind env command that prints the environment variables influencing cluster creation and the current value of each one. This makes it easier to discover provider, networking, and kubeconfig overrides from the CLI itself.\n\nTests cover unset, empty, and set values, and the root command now exposes the new subcommand.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ANISHSAJIKUMAR
Once this PR has been reviewed and has the lgtm label, please assign stmcginnis 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

[linux-foundation-easycla]

• ❌ - login: @ANISHSAJIKUMAR / name: anish kumar . The commit (3a0e254, 7f2ef97, b79d82b, bd87b77, c5d0e48) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

Hi @ANISHSAJIKUMAR. Thanks for your PR.

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

[stmcginnis]

Please stop including all previous commits in new changes. You will need to clean this up.

A similar approach has already been discussed and I believe there is an open issue with some more context. Make sure to check for existing work before proposing new.

If there is something like this you want to add, make sure you follow the process of filing an issue so it can be discussed prior to submitting actual PRs.

If these stacked PRs continue and there is no response then I am going to assume these are being entirely LLM drive and I will start to just close new PRs without further discussion.