[WIP] Validate PR with GitHub Actions.

[Et7f3]

This PR re-open #52 (because it started with a fork of @ulrikstrid branch)

Most notably Github Actions' cache is too limited. 500 megabytes is not enough for esy!

Originally posted by @wokalski in #52 (comment)

With #59 the cache tarball go from 420 Mo to 360Mo and can be cached. (see my actions run it run in 2 minutes after downloading esy)

d185e75 fix #58

What should be done

• Merge npm-publish.yml
• Add stale issue detection (just a message ?)
• Check that formatting is correct.
• Hook up release-drafter

[Et7f3]

In last I use the advanced template so feature, enhancement, fix, bugfix, bug, chore label can be added.

[Et7f3]

Ok I get 403 because it is not merged but it work fine in my fork Et7f3#2 (comment)

[Et7f3]

Regarding formatting, I think it's a good idea to add auto format. Pushing commits from CI is sort of controversial but overall it'll be a quality of life improvement +1.

Can we add a message from a bot like:

I've updated your test lock files and formatted the code. Please pull the last commit before pushing any more changes.

Done :)

[Et7f3]

You can customize message if you want :)

[wokalski]

That's extremely good. One thing, could you please organise the commits a bit more? Or should I just squash it all? There are quite a few changes. I suppose most of them are lock file related but nevertheless 🙂.

[Et7f3]

Lot of commits come from merge I will try rebasing so this noise disapear.