Publish to NPM registry.

[pauldruce]

Summary of changes:

• I've added a github workflow which will publish this project as a package on npmjs and the github npm registry.
  • This is essentially the same process that bats-core is using to publish as a node package.
  • This requires a secret called NPM_TOKEN for the existing project to work for the npmjs registry.
  • Publishing to the GitHub npm registry should work without any extra secrets.
• Listed bats and bats-support as actual dependencies, as bats-assert isn't much use without them.
• A smoke test of the npm installation was added to show it works.

This PR addressing #70 : bats-core/bats-core#1107

[pauldruce]

From looking at the current npmjs project. I expect that @jasonkarns should take a look at this, as in order to successfully publish to npmjs, we need an access token for the project.

[TurekBot]

I ran into #70 as well today; it'd be great if this PR could fix that.

Is @jasonkarns still the person that should look at this?

[TurekBot]

@jasonkarns, are you the person to take a look at this?

[jasonkarns]

Opened #81 to use the release workflow I've settled on for nodenv. Left some comments here so I can understand which additional pieces might still make sense to pull into that PR.

[jasonkarns]

ztombol is still the author of this package, even though he's not an active contributor. If we want to list the bats core org, they would be contributors, AFAIUI.

[pauldruce]

Ahh, so we should just add him to the contributors and remove the author field altogether? Author is a very singular sounding field, and this is no longer authored by one person/entity.

[jasonkarns]

closing with #81 having landed. but i appreciate the work put into this and the ideas shared within. will have followup PRs to reflect the package authorship cleanup and additional tests.