This is an attempt to develop a strategy for consuming Playground.

• Using the latest @wp-playground/client package from unpkg.com might break the existing sites when the methods change.
• Using a fixed version might break the existing sites if the remote API changes.
• Versioning the remote.html API seems like an overly complex maintenance burden.

Let's just have Playground ship its own API client that's compatible with the current version of Playground. It still doesn't address breaking API changes, but that is a separate discussion involving defining stable and unstable APIs.

This will involve an adjustment to the playground.wordpress.net build pipeline:

Done is:

• Running nx build:wasm-wordpress-net playground-website yields a build where the client.js library is exposed
• Any references to client.js coming from unpkg in this repo are updated to talk about https://playground.wordpress.net/client.js instead.