Semver timeout increased for single test

[alfonsograziano]

Checklist

• npm test passes
• contribution guidelines followed
  here

Even if we increased the overall Semver test suite timeout in #1004, some tests still fail due to timeout.
https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3318/nodes=rhel8-ppc64le/testReport/junit/(root)/citgm/semver_v7_5_4/

This change will bring the timeout for the single test to 60s.
I'm not sure if this is a proper solution, but we can give it a shot.

[codecov-commenter]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (b8193a7) 96.44% compared to head (5af659c) 96.44%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1013   +/-   ##
=======================================
  Coverage   96.44%   96.44%           
=======================================
  Files          28       28           
  Lines        2139     2139           
=======================================
  Hits         2063     2063           
  Misses         76       76           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[RafaelGSS]

What do you mean by single test? There are at least 3 tests failing due to timeout, is it reproducible in your machine?

[alfonsograziano]

I'm sorry for the poor choice of wording :) I mean that the single test failed due to timeout, not the entire citgm run. In fact, the citgm run finished after 3 min and 10 sec (with a 5 min timeout).

It is not reproducible on my machine unfortunately (since I'm using macOS).
Maybe @isaacs can help us?
Sorry for the ping, I see that you are mentioned as the maintainer of this package. Can you please take a look at the timeouts? I'm not sure if the solution I proposed can fix the issue or not