fix(makeServerFetchye): mask errors from server side fetching

[code-forger]

When a fetch fails in SSR, we now drop the error entirely. This prevents unserializable Errors ending up in the redux store.

This also provides a better behaviour for SSR where failed fetches still render a loading state, allowing the browser to 'try again' fetching the data

Motivation and Context

This removes a 'cannot serialize' error from being emitted on the server when a fetch fails.

How Has This Been Tested?

Using a local instance of one app and some test modules I have proved that SSR now renders a 'loading' state of the application, without logging 'cannot serialize' errors, when a fetch fails in the server.
I have Unit test coverage for all new code.

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (adding or updating documentation)
• Dependency update

Checklist:

• My change requires a change to the documentation and I have updated the documentation accordingly.
• My changes are in sync with the code style of this project.
• There aren't any other open Pull Requests for the same issue/update.
• These changes should be applied to a maintenance branch.
• I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using Fetchye?

None

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 2e59af6:

Sandbox	Source
quick-install	Configuration
fetchye-provider-install	Configuration
fetchye-redux-provider-install	Configuration
nextjs-fetchye-ssr	Configuration

[JAdshead]

I am happy to always have another attempt in the client if it errors on the server.