move errors to GraphQLWrappedError rather than context

[yaacovCR]

• preserves order of errors with respect to operation
• bubbling errors mask the non-bubbling errors such that extra information does not leak

[netlify]

✅ Deploy Preview for compassionate-pike-271cb3 ready!

Name	Link
🔨 Latest commit	6a913ce
🔍 Latest deploy log	https://app.netlify.com/sites/compassionate-pike-271cb3/deploys/6720c1fff05ae90008a6d766
😎 Deploy Preview	https://deploy-preview-4266--compassionate-pike-271cb3.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

Hi @yaacovCR, I'm @github-actions bot happy to help you with this PR 👋

Supported commands

Please post this commands in separate comments and only one per comment:

• @github-actions run-benchmark - Run benchmark comparing base and merge commits for this PR
• @github-actions publish-pr-on-npm - Build package from this PR and publish it on NPM

[yaacovCR]

oddly:

[yaacovCR]

I have rebased #4264 on top of this PR => both PRs seem individually to lead to a drop in performance for async iterator lists, but when combined, the drop disappears. @JoviDeCroock -- my thought is that the function is very sensitive, and so the benchmark in this case may not be reliable, but that overall if we can make the numbers work, we should be able to merge both PRs, and maybe we should open a separate issue to investigate?

[yaacovCR]

was able to remove this from the #4267 stack