INTMDB-503: Configurable cluster timeouts

[evertsd]

Description

Some cluster cases take well over 3 hours for changes to apply, this empowers people to set timeouts that work for them.

Link to any related issue(s):

Type of change:

• 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)
• This change requires a documentation update
• Documentation fix/enhancement

Required Checklist:

• I have signed the MongoDB CLA
• I have read the contribution guidelines
• I have added tests that prove my fix is effective or that my feature works per HashiCorp requirements
• I have added any necessary documentation (if appropriate)
• I have run make fmt and formatted my code

Further comments

[evertsd]

I have not actually had a chance to test this yet, though believe this is all the code that's needed and thought there was some merit to pushing up the code & opening this as a WIP

[andreaangiolillo]

LGTM

[Zuhairahmed]

Thanks @evertsd, can we also update Registry Docs (for both Adv Cluster + Cluster) to call out that timeouts are now customizable so customers know to leverage?

[evertsd]

Ok @Zuhairahmed that documentation has been added

[Zuhairahmed]

Thanks @evertsd, LGTM!