#3019 Updated default FlytePropeller subqueue base delay to 0 Pull request opened by hamersaw Describe your changes This PR updates the subqueue default configuration for FlytePropeller. This construct is used to queue a workflow when FlytePropeller detects a changein a node status. This can happen using a k8s watch over Pods to detect state changes. Currently, the configuration defaults to a 5s base-delay, this means that everytime an item is added to the queue, FlytePropeller waits 5s to process it, which results in unnecessary delays in workflow execution. The trade-off is more aggressive workflow evaluations. We have tested this change at some scale and do not believe this is too frequent, meaning FlytePropeller is overwhelmed by the number of workflows in the queue. However, if it does prove too small, this can be increased in the configuration. Check all the applicable boxes ☑︎ I updated the documentation accordingly. ☑︎ All new and existing tests passed. ☑︎ All commits are signed-off. flyteorg/flyte ✅ All checks have passed 9/9 successful checks