Make timeout for hashFiles() configureable

[Carsten-MaD]

As reported here #1840, in scenarios where a lot of files need to be hashed to build up a cache, the process running hashFiles() may run into the fixed 120 second timeout and be cancelled prematurely.

This pull request introduces a new parameter --timeout= that is meant to be passed the same way as the already existing optional parameter --follow-symbolic-links.

Example configuration for actions/cache:

- uses: actions/cache@v3
  with:
    key: ${{ runner.os }}-${{ hashFiles('--timeout=600', '**') }}

Points of discussion:

• It may be controversial to pass a parameter that affects the timeout of a process like this, as it is not directly related to the hashFiles() command itself, but rather to how it is run. If you see an alternative way of injecting such a parameter, please let me know.
• For this, I removed firstParameter and the connected logic. Instead, the logic now looks for if a parameter name starts with
  -- and tries to match one of the two expected parameters. Please let me know if you strongly feel the logic that these parameters need to be first is needed, I will then put something in.
• There are two different exceptions thrown for when the timeout number could not be parsed (e.g. a string passed), and when it was empty. This could be made into one more generic exception to handle and explain both.

[Carsten-MaD]

Not entirely sure, is there anything I need to do so the PR is reviewed, am I missing a step?

@TingluoHuang sorry if I tag you directly, maybe you can advise?

[JJ]

Just a typo.

[shubhank008]

This Pr is really needed for us large gamedev project users, any update on this ?

[gotchipete]

This Pr is really needed for us large gamedev project users, any update on this ?

Agree! (realizing I'm replying to a comment from 10 mo ago)

[haoming29]

Any updates for this issue or this should be closed? We caught the same error and suspect our runner fails because we have large files to hash and it could go over 120s in many cases.

[BE-Digital-Solutions-Bart]

Code seems good
This merge should solve issue #1840

[alb3rtuk]

Hey guys, we're running into the same issue with the 120 second hashFiles() timeout. Can we merge this please?

[Propagant]

So what's the status on this?

[AryanJ-NYC]

Bump?

[guicaulada]

Running into this as well, it's weird, with 4 vCPU it runs fine, with 32 vCPU (on a very large runner for extra heavy tasks) it fails, if I run the same task on a smaller runner, it succeeds, but the whole workflow takes much longer.

[Karsto-sys]

also would like to have this