Adding a helm login to packages reconcile flow for workload clusters

[pokearu]

Issue https://github.com/aws/eks-anywhere-internal/issues/2269:

Description of changes:
This solves part one of the issue when creating a workload clusters with an authenticated registry mirror. The EKS-A controller is responsible for performing a helm install of the eks-anywhere-packages helm chart for a workload cluster; this was failing because

1. We did pass the --insecure-skip-tls-verify flag during the helm install.
2. For authenticated registry mirrors; we did not perform a helm login before running the helm install.

The changes in this PR fixes both the issues, hence customers who use kubectl to create a workload cluster would now get have packages enabled successfully when having an auth registry mirror.

Testing:

eksctl-anywhere create cluster -f cluster.yaml --kubeconfig mgmt.kubeconfig --bundles-override bundle.yaml

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.43%. Comparing base (3fe6cc7) to head (b25874c).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7971   +/-   ##
=======================================
  Coverage   73.42%   73.43%           
=======================================
  Files         577      577           
  Lines       35821    35827    +6     
=======================================
+ Hits        26302    26308    +6     
  Misses       7854     7854           
  Partials     1665     1665           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[tatlat]

/lgtm
/woof

[eks-distro-bot]

@tatlat:

In response to this:

/lgtm
/woof

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/test-infra repository.

[abhay-krishna]

/lgtm
/approve

[eks-distro-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhay-krishna

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [abhay-krishna]

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

[pokearu]

/cherry-pick release-0.19

[eks-distro-pr-bot]

@pokearu: new pull request created: #8028

In response to this:

/cherry-pick release-0.19

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/test-infra repository.