Listing an array of authors in package.json breaks some tools that parse it

Hi! While upgrading some dependencies in our project, I noticed an issue with the metadata for this package that caused our build process to crash after the upgrade.

Specifically, according to the [npm documentation](https://docs.npmjs.com/cli/v9/configuring-npm/package-json#people-fields-author-contributors) the `author` field in package.json should designate a _single person_ and be either a JSON object or a string. This package currently has `"author": ["nkbt", "chenglou"]`, which violates the spec and crashes some tools that try to parse it according to the spec (such as https://github.com/pivotal/LicenseFinder). While such tools should probably be made more robust, the current package.json for this project is (AFAICT) still invalid.

Probably the simplest fix would be to change the key from `"author"` to `"contributors"`, which has the same semantics but allows multiple values. It could also be a good idea to validate the package.json against https://www.npmjs.com/package/package.json-schema.

Inspect package.json and compare its people fields with the npm package.json documentation linked in the issue. Validate the metadata against the referenced package.json schema; done means the author field represents one person, contributors holds the multiple names, and spec-compliant tools no longer fail.

Written by the indexing model from the issue text.