Ingress properties being overridden when updating a Container App
This was due to previous usage of the az containerapp ingress enable command, which performs a PUT operation on the ingress property and was always being ran after updating an existing Container App
Now we will be running az containerapp updateonly when we find that neither ingress nor targetPort were provided by the user, otherwise we will defer to using az containerapp up
Non-existent resource groups weren't being created in the simple creation scenario
This PR aims to resolves the following issues:
az containerapp ingress enablecommand, which performs aPUToperation on theingressproperty and was always being ran after updating an existing Container Appaz containerapp updateonly when we find that neitheringressnortargetPortwere provided by the user, otherwise we will defer to usingaz containerapp up