current way of disabling telemetry via config.yaml is not sufficient as these files get changed during test execution and that might trigger sending metrics to telemetry which needs to be avoided.

More discussion in here: https://redhat-internal.slack.com/archives/C03CJTNLKAT/p1741901272997509

The pull-secret is setup in different ways depending on the type of MicroShift build or deployment:

Bootc images:
pull-secret from Jenkins credentials in the microshift-build-bootc-images job
scp'd to the build hosts
Remove cloud.openshift.com before the SCP

ISO images:
pull-secret scp'd from Hypervisor in the microshift-create-buildvm job
Remove cloud.openshift.com right after the scp from the Hypervisor
When the microshift-build-images job runs the build_and_cache_microshift_images script, it uses the ~/.pull-secret.json that's already on the build host
Does a sed replace into the kickstart file

rpm-ostree and RHEL OS:
pull-secret from Jenkins credentials in the microshift-install-upgrade job
scp'd to the build hosts
Remove cloud.openshift.com before the SCP