[Core feature] Set FlytePropeller node and workflow deadlines to infinite

[hamersaw]

Motivation: Why do you think this is important?

FlytePropeller uses a few configuration values, namely node-execution-deadline, node-active-deadline, and workflow-active-deadline to restrict the runtimes of workflows and nodes. These configuration are applied during long-running node and workflow executions. Currently, the defaults are 48h for node deadlines and 72h for workflow deadlines. The issue is that users with long-running tasks / workflow experience unintended terminations under the default configuration.

Goal: What should the final outcome look like, ideally?

These deadline configuration values should be set to 0 by default, effectively disabling them and setting the deadlines to infinity. Therefore, users with long-running tasks/workflows will not experience unintended terminations.

Describe alternatives you've considered

Leaving it as is provides some level of sane configuration, but results in unintended termination for some users.

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[AyushK-101]

I would like to work on this

[Ln11211]

@hamersaw I opened a PR , could you please review it? :)