Description of problem:
Currently, plugin timeout is hardcoded to 300 seconds. That is:
1) too low in my eyes as it matches default command execution timeout - if one command within a plugin timeouts, the whole plugin does so and rest of commands are not even attempted to be collected

2) not configurable, what makes problem to systems with e.g. huge journals or others where a plugin is expected to run longer (like foreman that calls foreman-debug with timeout=900).

I suggest making the timeout double (open to other values) and to have it configurable via SoSOptions / cmd line options.


Version-Release number of selected component (if applicable):
sos-3.6-9


How reproducible:
100%


Steps to Reproduce:
1. Have a system with big journals / foreman-debug taking long time (well here it doesnt matter as foreman plugin does not collect anything else..) - such that some early cmd run timeouts
2. run sosreport
3. try to change the timeout


Actual results:
2. the early cmd and plugin timeouts and subsequent cmds from it are not attempted to be collected
3. no way to configure the plugin timeout


Expected results:
2. the early cmd timeouts, plugin continues in firing next cmds until some higher timeout
3. plugin timeout is configurable


Additional info: