feat: Remove IE11 support

[kitten]

Summary

This PR aims to comprehensively deprecate the family of urql packages' support of Internet Explorer 11, which has now reached its end of life officially.

Our main focus is that no upgrade is required. We're currently at a stable state and we do not expect that users who need to continue supporting IE11 for a little while longer will need to upgrade immediately.

As part of this change we want to remove code that was added or written in a such a way to enable IE11 support, for compacter alternatives, update our build scripts and tooling, and perform a general cleanup.

Set of changes

• Update buble transpilation and Terser output config
• Remove unused babel transformations
• Fix cjs-module-lexer plugin and improve output
• Remove IE11 code from @urql/exchange-persisted-fetch

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: 0667a26d907828bae96c034d7da0da78eb514b82

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

This PR includes changesets to release 19 packages

Name	Type
@urql/exchange-graphcache	Major
@urql/exchange-persisted-fetch	Major
next-urql	Major
@urql/preact	Major
urql	Major
@urql/storybook-addon	Major
@urql/svelte	Major
@urql/vue	Major
@urql/exchange-auth	Major
@urql/exchange-execute	Major
@urql/exchange-multipart-fetch	Major
@urql/exchange-populate	Major
@urql/exchange-refocus	Major
@urql/exchange-request-policy	Major
@urql/exchange-retry	Major
@urql/core	Major
@urql/introspection	Major
urql-docs	Major
@urql/storage-rn	Major

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

[kitten]

cc @JoviDeCroock: As discussed, this now uses wonka@^6.0.0 which is so far 100% backwards compatible but ported to TypeScript to make external contributions easier and further reduce its bundle size impact. This is explicitly marked as a major (breaking change) separately. That said, we don't have to mark it as breaking on any exchanges, since it'll only lead to duplicate versions but no breakage. So, we can further discuss how we'd like to handle the changeset itself 🤔