chore: make helm timeout backward compatible

[ricardomaraschini]

Description

in the past the helm chart install timeout was moved from an integer to a string. this commit brings back the capability of using integers to set the helm chart timeout.

Type of change

• Chore
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

• Manual test
• Auto test added

Checklist:

• My code follows the style guidelines of this project
• My commit messages are signed-off
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

[twz123]

Breaking the API was a deliberate decision back in the day. Maybe the old assessment is no longer valid?

[ricardomaraschini]

Breaking the API was a deliberate decision back in the day. Maybe the old assessment is no longer valid?

We have been using the old API (timeout as integers) to allow users to set up timeouts for their helm charts. This breaking change without a correspondent CRD version change really broke our legs :-( I was trying to see how hard it would be to make this work with both integers and strings but it seems more complex than I anticipated.