Always throw network errors in useSupenseQuery regardless of the error policy

[jerelmiller]

Closes #10384

Updates useSuspenseQuery to always throw network errors, regardless of the errorPolicy set in options. This is more in-line with how useQuery works when encountering a network error since the error is retained and the onError callback is called.

Checklist:

• If this PR is a new feature, please reference an issue where a consensus about the design was reached (not necessary for small changes)
• Make sure all of the significant new logic is covered by tests

[changeset-bot]

🦋 Changeset detected

Latest commit: 94c57f8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@apollo/client	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[jerelmiller]

The logic felt a bit heavy when reading this all inside the if below. That being said, there are so many names here, its hard to keep coming up with new ones. If you have a suggestion for a better name for this variable, I'd love to hear it! At the very least, I want to make sure the if statement below reads nicely and is easily understandable. If not, please let me know how I can update this to make it easier to understand the logic here.

[alessbell]

LGTM!