Fix version, update deps, switch to ncc, release 1.3.1

[kolyshkin]

Having node_modules in the repo is problematic. For one thing,
dependabot updates dependencies in package.json, but the old versions of
modules are still there in node_modules.

To fix this, let's switch away from having node_modules in the repo to
using ncc, as they recommend in [1] and [2].

Fix package version in package.json while we're at it.

This commit is mostly auto-generated, the only manual edited files are
package.json and .gitignore. Here is the workflow (using npm 8.9.12):

        $EDITOR package.json
        $EDITOR .gitignore
        git add .gitignore
        git rm -rf node_modules
        rm package-lock.json
        npm i
        npm i @actions/core # bump actions/core version
        git add dist
        git commit

NOTE that this also upgrades @actions/core to the latest 1.x release
(which is 1.10.x at the moment), which probably fixes the issue of GHA
warning about the use of deprecated set-output command. This happens
because ^1.0.9 means "latest 1.x" in npm.

These changes are tested here: https://github.com/opencontainers/runc/actions/runs/6017455860/job/16367756745

[1] https://github.com/actions/javascript-action/tree/main
[2] https://docs.github.com/en/actions/creating-actions/creating-a-javascript-action

PS I know very little about js, npm, ncc, github actions etc. I was just tired that every time I am getting this warning:

The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

and decided to do something about it.

While at it, I would like to point out that @actions/github dependency used by this repo is obsoleted (also, the code in this repo does not work with its newer versions).

[kolyshkin]

@Tim-Zhang PTAL 🙏🏻

Once this is merged, dependabot can be set up to automatically update dependencies -- meaning all you need to do is merge dependabot PRs and cut new releases from time to time.

[kolyshkin]

In fact, dependabot is already enabled for this repo, but due to the fact we currently have node_modules directory, dependabot is not really updating anything. This PR fixes it.

[Tim-Zhang]

@kolyshkin Thanks and LGTM

[Tim-Zhang]

@kolyshkin I have invited you as the maintainer of the org, if you would like to help with maintaining this project, I would be very appreciate.

[kolyshkin]

@kolyshkin I have invited you as the maintainer of the org, if you would like to help with maintaining this project, I would be very appreciate.

Sorry I missed it, can you please re-send?