Add create-widget script, fix package publication and add local dev registry

[AlanSl]

This PR does three interlinked things:

• Fixes a number of configuration details so that everything works smoothly both locally through Lerna sibling links and when published and pulled in from a registry, so builds are a reasonable size, and so dependencies like react and shared-components don't get duplicated through dep chains (a common source of bugs if not done right).
• Adds a create-widget script that creates a new ready-to-use widget in a new repo with everything set up
• Adds Verdaccio for local development and publishing with some scripts for local testing, publishing and unpublishing packages to the local registry

After this, someone developing a widget can go from an empty directory to a new widget with dev env ready to start with a one-line command:

1. In a new empty directory (mkdir some-widget && cd "$_"), use NPM’s init script (or yarn create also works): npm init @libp2p-observer/widget
2. CLI wizard allows optionally changing the widget name (default is directory name), description, author, licence etc through CLI wizard

3. Install dependencies with npm i (after public publication) or npm i --registry="http://localhost:4873/" (while using the local registry described below)
4. Start storybook with npm run storybook and get developing

The widget demo in storybook is hooked up to a data sample complete with shell and other config such as linting already set up matching the main project. The default widget has some example content demonstrating how a typical component looks and allowing the user to easily explore available data:

This also allows people working on the main project to conveniently test publishing before publishing to a public repo:

1. Spin up verdaccio with npm run start:verdaccio, which uses docker and stores local registry content in gitignored ./verdaccio/storage where published tarballs can be easily inspected
2. Develop as before using npm run storybook:component-name and npm run start:catalogue for hot-reloading demos
3. When ready to try out a published package, npm run local-publish
4. Test everything from the local registry, for example following the above steps but with npm install --registry="http://localhost:4873/" instead ofnpm i`
5. If there’s a problem with builds and bundles when pulling from the registry, make changes then do npm local-unpublish then npm local-publish to try again.

As well as easy local file storage access to locally published test packages, they can be browsed using the Verdaccio UI:

[AlanSl]

Latest commits fix merge conflicts and most tests, for the other tests I need to generate new samples.

[AlanSl]

With the last couple of commits this beast should be ready to review. Tests pass locally, failing on CI because I think GitHub Workflow is for some reason trying to install from the pubishConfig registry, which isn't available until we can do npm run start:verdaccio, which we ideally wouldn't want to do and can't do until the deps are installed anyway...

I don't think any of us actually have time to review today so I'll come back and fix that later and prioritise making more ground on the next PR!

[AlanSl]

Latest commits add in latest Master, fix some issues there with using the new protobuf, and fix CI.

I'll fill in the missing tests and docs when I'm back on Wednesday.

[AlanSl]

As discussed I'll merge this as-is to keep momentum on the design implementation, and I've added tickets to Trello for updating the docs and package readmes and for the test on the create-widget CLI itself