Remove dependency on jest-each

[ericcornelissen]

Description:
Change the dependency on jest-each from a regular dependency to a development dependency (devDependency) as it is only used in tests. Remove the dependency on jest-each in favor of Jest's builtin test.each functionality.

Related issue:
This relates to #394 which introduced jest-each as a dependency.

Check list:

• Mark if documentation changes are required.
• Mark if tests were added or updated to cover the changes.

[ericcornelissen]

As a second suggestion, the functionality of jest-each has been part of the Jest core since v23 (ref). For the version of Jest used in this project (as well as later versions) it is available as test.each.

I did not see the decision to use the package jest-each over the built-in test.each function being discussed in #394. I'd propose to make that switch, if you agree I can update this Pull Request accordingly.

As a reference, the diff would look something like (in addition to removing the dependency on jest-each altogether):

  import path from 'path';
  import fs from 'fs';
- import each from 'jest-each';

  jest.mock('@actions/core');

...

    });

-   each([
+   test.each([
      [new HttpError('Error message')],
      [new NotFound('Error message')]
-   ]).test(
+   ])(
      'should warn if configuration file could not be fetched through the API, log error and fail the action',
      async error => {

[IvanZosimov]

Hi, @ericcornelissen 👋 Thank you for noticing this! For sure, please, switch the code to use the built-in test.each. Moreover, in that case, jest-each can be removed from the list of dependencies completely.

[ericcornelissen]

For sure, please, switch the code to use the built-in test.each. Moreover, in that case, jest-each can be removed from the list of dependencies completely.

Done and done 🙂