Update Pipeline Templates to Avoid Deploying both Istio Versions

istioCore cannot be deployed alongside istio, however, with the current configuration of the All Packages this will end up occurring. In order to solve this we will need to:

• Update the logic for the All Packages label such that only one or the other deploy. Ideally, it should default to istio leave istioCore disabled.

It may also make sense to create a method by which the reverse can be done. For example, adding a label of istioCore could enable the new istio functionality via the pipeline while disabling istio.

This may also include looking into how the big bang pipeline decides how and what to enable as it appears to add any packages where any changes have been made which would be problematic in situations where changes to both have been made.