Feature: parse messages as json

[ThisIsMissEm]

New feature description

• Parses the websocket messages as JSON, instead of leaving this to the end-user
• Correctly documents events emitted from the WebsocketNotification class
• Switch to getWellKnownSolid from solid-client to work across both ESS 1.1 and ESS 1.2
• Fix unit tests (migrate from jest-fetch-mock which caused issues for e2e tests)
• Fix & re-enable e2e browser and node.js tests
• Drop support for Node.js v12 (end of life)
• Migrate CI/CD to use new environments (ESS PodSpaces & ESS PodSpaces Next)

Checklist

• All acceptance criteria are met.
• Relevant documentation, if any, has been written/updated.
• The changelog has been updated, if applicable.
• New functions/types have been exported in index.ts, if applicable. n/a
• New modules (i.e. new .ts files) are listed in the exports field in package.json, if applicable. n/a
• New modules (i.e. new .ts files) are listed in the typedocOptions.entryPoints field in tsconfig.json, if applicable. n/a
• Commits in this PR are minimal and have descriptive commit messages.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
solid-client-notifications-js	✅ Ready (Inspect)	Visit Preview	May 4, 2022 at 2:55PM (UTC)

[kay-kim]

Hey @ThisIsMissEm - just left a little comment about the landing page blurbs. You might want to work with @nicolasmondada about how to position the product.

[ThisIsMissEm]

This was broken for some reason and I couldn't get it working for the life of me. This is probably not important.