Bug: Large responses break node clients using node-fetch

[SgtPooki]

figured out multiple issues:

1. web3.storage response times are high because you're sending back huge chunks of data that they don’t need to. (Check actual response data vs parsed response data in web3 pinning service returns invalid PinStatus object #1221 (comment))
2. This causes node-fetch to fail silently when trying to response.text() regardless of try/catch blocks, .then(_, catchHandler), or even .catch() handlers.
   • Found Reponse.text() hangs if you've cloned the response node-fetch/node-fetch#1131 which pointed me to https://github.com/node-fetch/node-fetch#custom-highwatermark

   • it will hang with large response in Node.

   • I updated highWatermark to 2mb and also added a promise race with a timeout of 15 seconds and seem to have finally gotten around the silent crashes when testing web3

Related to ipfs-shipyard/pinning-service-compliance#29

[SgtPooki]

fixing item 1 is a breaking change for any existing users depending on that extra information, so to be fully compliant with the pinning service spec, you may need to stand up a different endpoint