fix: persist binariesLocation for AWS and GCE in v1alpha2

[madhoshyagnik]

What this PR does / why we need it:

Fixes #18736.

spec.cloudProvider.aws.binariesLocation and spec.cloudProvider.gce.binariesLocation existed in the internal API and v1alpha3, but lacked a representation in the v1alpha2 API.
Because kOps persists cluster specs to the state store in the v1alpha2 format, these fields were silently dropped on every write, making them unreachable in standard workflows.

This PR adds AWSBinariesLocation and GCEBinariesLocation to the CloudConfiguration struct in pkg/apis/kops/v1alpha2/componentconfig.go (next to other AWS/GCE-specific settings like DisableSecurityGroupIngress and GCEUseStartupScript). It also includes the necessary manual conversions in pkg/apis/kops/v1alpha2/conversion.go to ensure BinariesLocation successfully round-trips to and from the internal CloudProvider struct.

Which issue(s) this PR fixes:

Fixes #18736

Special notes for your reviewer:

Ran make apimachinery to regenerate conversions and deepcopies.

[kubernetes-prow]

Welcome @madhoshyagnik!

It looks like this is your first PR to kubernetes/kops 🎉. 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/kops 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. 😃

[kubernetes-prow]

Hi @madhoshyagnik. 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.

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.

[kubernetes-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 assign zetaab 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

[ameukam]

/ok-to-test

[ameukam]

@hakman do we want to keep parity of alpha2with alpha3 ?