update to handle graphql v16_x breaking changes

[bueche]

Description

The purpose of this PR is to upgrade join-monster to support graphql@16_6_0. There were a number of breaking changes introduced in graphql version 16 that had a major impact (mostly) to the tests and to some of the code in join-monster. This PR fixes these changes so the tests pass. I can't guarantee that other breaking changes were not caught by the tests.
Some of the breaking fixes of graphql v16:

1. Remove support for positional args in graphql/execute/subscribe func graphql/graphql-js#2904. This was, by far, the largest change as it broke most tests due to their reliance on lodash partial. I just removed that dependency and fixed the parameters so that they would align with the v16 approach. So for example:

import { partial } from 'lodash'
    const run = partial(graphql, schemaBasic)
    const { data, errors } = await run(query) <--- old approach

was changed to:

      const { data, errors } = await graphql({schema, source}) <--- new approach

2. Fragment tests failed due to a change in structure. I couldn't find the PR in graphql that impacted this one but the changes were mostly the main join-master index.js. Without these changes a number of the relay tests failed with the following error: def.args is not iterable and some code in graphql was added to iterate through this structure which in most cases was an array (only the failed cases were not an array). So I changed this definition to be an array (see src/index.js change.

3. Other fragment tests failed with Support for returning GraphQLObjectType from resolveType was removed in graphql-js@16.0.0 please return type name instead and this was fixed also in src/index.js to add name to type.

4. An error occurred: TypeError: Class constructor GraphQLNonNull cannot be invoked without 'new' that was fixed as well.

Testing

To test this change it is necessary (still) to use node v14 (nvm use 14).

It is important to ensure that graphql@16_6_0 is installed.

I ran the following suites:

• npm run testsqlite3
• npm run testpg
• npm run testpg-paging (postgres)
• npm run testmysql and
• npm run testmysql-paging (mysql)

all passed, except for the offset cursor tests in mysql which were throwing an error This type of pagination not supported on this dialect which is a join-monster error and I believe expected.

• This change adds test coverage for new/changed/fixed functionality (note: I did not add any new tests as the code and tests were just updated to support the breaking changes of graphql v16)

Checklist

• I have added documentation for new/changed functionality in this PR via comments and by updating the change log