Cleanup catapult vars and make calls in cap-ci/

[viccuad]

This PR:

• Removes a bunch of uneeded env vars that we found when debugging an AKS deployment
• Removes DEFAULT_STACK=cflinuxfs3 for eirini, as newer kubecfs will not need it. See cloudfoundry/cf-smoke-tests#61
• Switches catapult calls from make scf* to make kubecf*

[viccuad]

Thanks! We can postpone this if it's going to create conflicts; the only functionality change is taking out the default stack setting to cflinuxfs3.

The change from make scf* to make kubecf* is cosmetic, as SCF_OPERATOR=true make scf* is aliased to make kubecf* in catapult directly.

For the rest of scf references, I would separate them in internal to catapult (the name of scf-config-values.yaml and chart folders inside of buildfolder etc) and external, such as all the SCF_* env vars. The first ones can be refactored transparently out of the pipeline. For the latter ones I would prefer to add aliases like KUBECF_* := SCF_* or CF_*, so people don't have breakages and don't need to relearn the UI until a catapult v2.

[bikramnehra]

Thanks! We can postpone this if it's going to create conflicts; the only functionality change is taking out the default stack setting to cflinuxfs3.

The change from make scf* to make kubecf* is cosmetic, as SCF_OPERATOR=true make scf* is aliased to make kubecf* in catapult directly.

For the rest of scf references, I would separate them in internal to catapult (the name of scf-config-values.yaml and chart folders inside of buildfolder etc) and external, such as all the SCF_* env vars. The first ones can be refactored transparently out of the pipeline. For the latter ones I would prefer to add aliases like KUBECF_* := SCF_* or CF_*, so people don't have breakages and don't need to relearn the UI until a catapult v2.

We can discuss this in catapult meeting.

[viccuad]

Closing since https://github.com/SUSE/cap/pull/27 got in.