feat: extract Editor component into core package

[octokatherine]

closes #100

This PR pulls the UI in the screenshot below into a separate React component inside the core run-wasm package.

A user could import this component from the package to use this default interface. import { Editor } from '@run-wasm/runwasm'

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/sliphq/run-wasm/28TfVzUmjYNNF4YmCuHNeq9YrC7F
✅ Preview: https://run-wasm-git-fork-octokatherine-package-editor-ui-sliphq.vercel.app

[octokatherine]

Since we're using a local linked module for run-wasm, we have to run this script to tell the run-wasm module to use the example-nextjs project's copy of react. Users using the run-wasm npm package won't have to do this linking because the peer dependency should Just Work.

[kennethcassel]

Great work @octokatherine!

@all-contributors add @octokatherine for her code contributions

[allcontributors]

@kennethcassel

I've put up a pull request to add @octokatherine! 🎉