Evaluate removing VolumeSizeRequestTimeout config

[wdbaruni]

Jobs would fail if fetching inputs take more than 2 minutes, which is the default value here. Users who submit the job don't have any way to override this value as it is a configuration in the compute side. Even if they increate the overall job execution timeout using --timeout flag, the job will fail if the result is not downloaded within 2 minutes.

Maybe we should evaluate removing this configuration and just allow users and operators to set the overall --timeout value instead of having to expose different timeouts. I understand there might be use cases where the job shouldn't run if the results are not fetched within a certain period, but those will be very few cases, and will be better to simplify the overall user configuration and nobs they have to change

[wdbaruni]

part of #4014