v3: podSpecPatch can result in failed workflow

[alexec]

Pod "deploy-pipeline-kq79f-807066115" is invalid: [spec.containers[0].env[0].valueFrom: Invalid value: "": may not be specified when value is not empty, spec.containers[1].env[0].valueFrom: Invalid value: "": may not be specified when value is not empty

This workflow fails:

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: hello-world-
  labels:
    workflows.argoproj.io/archive-strategy: "false"
spec:
  entrypoint: whalesay
  templates:
  - name: whalesay
    podSpecPatch: |
      {"containers":[{"name":"main","resources":{"limits":{"cpu":"500m","memory":"250Mi"}}},{"name":"wait","resources":{"limits":{"cpu":"500m","memory":"250Mi"}}}]}
    container:
      image: docker/whalesay:latest
      command: [cowsay]
      args: ["hello world"]

[alexec]

You can fix this issue by changing the order of containers in podSpecPatch:

BAD:

      {"containers":[{"name":"main","resources":{"limits":{"cpu":"500m","memory":"250Mi"}}},{"name":"wait","resources":{"limits":{"cpu":"500m","memory":"250Mi"}}}]}

GOOD:

      {"containers":[{"name":"wait","resources":{"limits":{"cpu":"500m","memory":"250Mi"}}},{"name":"main","resources":{"limits":{"cpu":"500m","memory":"250Mi"}}}]}

[alexec]

Could have been introduced by:

fix(controller): Fix podSpecPatch (#5360) d828717

[alexec]

Created an upstream issue. golang/go#46146