chore: update npm-run-all to npm-run-all2

[strangelookingnerd]

This PR aims to replace npm-run-all which is no longer maintained (https://github.com/mysticatea/npm-run-all - last release November 2018).
The replacement npm-run-all2 can be used as a replacement that is still actively maintained (https://github.com/bcomnes/npm-run-all2 - last release October 2023)

npm-run-all2 why?

A maintenance fork of npm-run-all. npm-run-all2 is a fork of npm-run-all with dependabot updates, release automation enabled and some troublesome babel stuff removed to further reduce maintenance burden. Hopefully this labor can upstream some day when mysticatea returns, but until then, welcome aboard!

Please note that I created this PR semi-automatically across all applicable projects in https://github.com/camunda and https://github.com/camunda-community-hub

Feel free to ping me if you find any issue with it or simply ignore it.

[nikku]

Thanks for this PR.

Please note that I created this PR semi-automatically across all applicable projects in https://github.com/camunda and https://github.com/camunda-community-hub

A great approach would be to give us a heads-up, let us assess the situation, and then follow-up with the automation brute force approach 🙂

[strangelookingnerd]

Fair point 😄 For future reference, what would be the best way to give a heads-up?

[nikku]

A single PR to start the discussion, per org.

[nikku]

Thanks again for opening this PR. We'll assess it.

I closed your other PRs pending our assessment.

[nikku]

Thanks again for opening this PR. Checking out the update on this particular repository I found that some more housekeeping was necessary. Incorporated the update via 5142ada.

It is now also pulled in via automated dependency updates; so no need to create follow-up automated PRs on your end.