Narrow down --insecure-skip-tls-verify flag usage

**What happened**:
EKS Anywhere currently applies --insecure-skip-tls-verify in helm for image push, pull, and install. This would apply the flag to everything, regardless of whether registry mirror is being used or whether it is insecure.

**What you expected to happen**:
--insecure-skip-tls-verify flag should only be applied when registry mirror is use, and only when specified by the user to use it for the mirror.

**How to reproduce it (as minimally and precisely as possible)**:
Running EKS Anywhere in verbose mode shows the flag being in use via cli-tools container

**Anything else we need to know?**:

**Environment**:
- EKS Anywhere Release:
- EKS Distro Release:

Start by tracing the Helm image push, pull, and install commands invoked through the cli-tools container, then identify where --insecure-skip-tls-verify is applied. Compare that behavior with registry-mirror configuration and the user's insecure-mirror setting. Done means the flag is limited to an explicitly configured insecure registry mirror rather than applied to every operation.

Written by the indexing model from the issue text.