Use the max interval from the applications release.interval as an input to the defaultExecutor timeout

[nitishm]

Describe the bug
A clear and concise description of what the bug is.
Increase the

To be on the cautious side, pass the timeout to the defaultExecutor by finding the maximum duration using the release.interval from across the applications in the applicationgroup

To Reproduce
Steps to reproduce the behavior:
n
Expected behavior
A clear and concise description of what you expected to happen.
n/a

Screenshots
If applicable, add screenshots to help explain your problem.
n/a

Environment (please complete the following information):

• Kubernetes Version [e.g. 1.21.0]
• Kubernetes Distro [e.g. AKS, GKE, etc.]
• Orkestra Version Tag
• Helm Version

Additional context
Add any other context about the problem here.