Bumps [actions/setup-node](https://github.com/actions/setup-node) from 2.5.0 to 2.5.1.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@v2.5.0...v2.5.1)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

This change makes sure that we always use the same version of the `node` base-image for testing by making it explicit against which version of the image we're going to run our tests. 

Not specifying the version by explicit hash can for example cause issues when a local Docker cache has a very old version of the image, which causes the tests to fail.

In addition, we also configure Dependabot to automatically open version bump PRs for this testing image.

Bumps [semantic-release](https://github.com/semantic-release/semantic-release) from 18.0.1 to 19.0.2.
- [Release notes](https://github.com/semantic-release/semantic-release/releases)
- [Commits](semantic-release/semantic-release@v18.0.1...v19.0.2)

---
updated-dependencies:
- dependency-name: semantic-release
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

Allows running `npm run test:docker` to run the test-suite in Docker.

…timeout

The help text suggests that one should be able to configure an indefinite timeout by setting it to zero. However, the current implementation would immediately timeout while doing so.

This change ignores the timeout behaviour when the timeout argument is set to 0. In addition, a test is added which tests whether the timeout at least doesn't immediately time out.

## [2.2.2](v2.2.1...v2.2.2) (2022-01-21)

### Bug Fixes

* **timeout:** resolve degredation which prevented setting indefinite timeout ([b45e76c](b45e76c))