fix(service-error-classification): add TypeError as transient error

[siddsriv]

Issue #, if available:
Internal JS-5890

Description of changes:
fetch API surfaces connectivity errors as TypeErrors, example: TypeError: Failed to fetch in Chrome.

For browsers, we should retry for connectivity issues (offline), this is a fix to retry on TypeErrors then. Since we don't want to retry for TypeErrors that aren't network errors, I've paired this check with the actual error messages that different browsers surface (not an exhaustive list, but covers some major ones).

Fetch has an open issue about this: whatwg/fetch#526

additional resources

• https://stackoverflow.com/questions/61113344/fetch-api-how-to-determine-if-an-error-is-a-network-error

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.