Updating JS host payloads and simple examples

[brooksmtownsend]

This PR is an effort to update topics, cloudevent payloads, and READMEs to make this host easy to run and simple to hook into an existing wasmCloud lattice.

So far I've

• Renamed the old simple example to console since all interaction goes through the browser console. It's great to keep this example since it has sample config for esbuild, webpack, and importing
• Added more to the console example including a simple web UI for launching a host. The goal is for this example to be an easy way to run a single command and have a running JS host
• Updated the host_started and heartbeat payloads to include friendly name and labels

TODO

• Update actor_started payloads to include claims and required info
• Update actor_stopped payloads to include claims and required info (can be in a future PR since you can just refresh the tab to stop an actor 😉
• Ensure this host can listen to topics like start_provider to return an error message, get inventory to respond with its contents, and the auction topic to accept actors and not capability providers (can be in a future PR)
• Bundle the host into a simple React app or similar to show how this might look in a JS framework (added simple example)
• See what this could do with https://github.com/inokawa/react-native-react-bridge (unfortunately, very outdated)
• In the root level of this repository, add a simple script like cd examples/console; docker compose up -d; npm install; npm run start. Need to include prerequisites
• See about updating the npm JS library so other people could embed this host