Fix bonding notification error

[adamsoffer]

What does this pull request do? Explain your changes. (required)
This PR fixes an issue on staging where a bonding notification error appears even in the case where a transaction is successfully confirmed. The issue was caused by a breaking change in graphql-js v14.0.0 where servers that used to accept incorrect variable values now return errors to clients.

Specific updates (required)

• Updated the bond mutation so that it returns the correct custom scalar type (JSON as opposed to Boolean).
• Regenerated the graphql-sdk README and docs

How did you test each of these updates (required)

• Received a success notification after successfully bonding in the explorer
• Received a success notification after successfully unbonding in the explorer
• Received a success notifcation after successfully claiming rewards in the explorer
• Reran graph-sdk tests

Checklist:

• I have read the CONTRIBUTING document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.

[Randy1Burrell]

This change looks good.