Fixes #905

[stevefan1999-personal]

TODO:

• Make sure all of the significant new logic is covered by tests
• Rebase your changes on master so that they can be merged easily
• Make sure all tests and linter rules pass
• Update CHANGELOG.md with your change. Include a description of your change, link to PR (always) and issue (if applicable). Add your CHANGELOG entry under vNEXT. Do not create a new version number for your change yourself.
• If this PR is a new feature, reference an issue where a consensus about the design was reached (not necessary for small changes)

This PR addresses the issue on remote schemas that primitive values are being wrongfully annotated with a symbol whenever there is an error, and it also addresses error resolution to use the server-provided diagnostic information whenever possible (location is still resolved on the stitching proxy side) or otherwise, fall back to the old behavior (i.e. join error messages with newlines).

[apollo-cla]

@stevefan1999: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/

[apollo-cla]

@stevefan1999: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/

[stevefan1999-personal]

Can I not provide the mailing address? I don't want my personal information be invaded by another inch...

[stubailo]

Hi, can you please add a description for what issue this PR is intended to fix? I see some of the discussion in #905 but it's hard to follow what the specific issues are that this is addressing. That way, I can review if the intended outcome was achieved.

[stevefan1999-personal]

cc @stubailo I've updated my PR description and merged the ChangeLog, there are two little things to fix in a nutshell.

[yaacovCR]

Closed in favor of #1307