feat(controller): retry strategy support on daemon containers, fixes #13705

[MenD32]

Addresses #13705
And #2963

Motivation

Add retryStrategy support to daemon container templates.

Some use cases require argo workflows features that aren't supported in resource template, f.e.

• pod logs, statuses, and fails in the UI
• passing input artifacts into the daemon container

Modifications

execution functions now consider "succeeded" daemoned nodes as failed

When a daemoned container completes execution, it is considered as failed, if it has a retry strategy it will retry.

the IP change in the node will cascade down to future executions.

Verification

e2e tests

also for manual verification I added an examples to test and see the behavior locally

• examples/dag-daemon-retry-strategy.yaml
• examples/steps-daemon-retry-strategy.yaml

I simulated daemon failures by deleting the daemon pod manually

[MenD32]

i added an E2E test and i can't get it to work on the CI (even though make test-functional works locally), any clue why?

the behavior of the controller is as if its built on main instead of on this branch

edit: NVM got it to work