Create a unified repo for web components, move existing projects into it

[pkalita-lbl]

Currently the web components we produce are divided into two repos, wc-gocam-viz and wc-ribbon. Those two repos, in turn, have different structures. The wc-gocam-viz repo contains one project (meaning one package.json file, publishing one package to NPM) which defines multiple web components. On the other hand, the wc-ribbon repo contains multiple projects and each one defines a single web component. In other words, wc-ribbon is almost structured as a monorepo, except that there is no top-level tooling to manage its development and release workflows.

This task is to establish a new repository to house all GO web component development. Decisions to be made as part of this task:

• Naming: something like geneontology/web-components or something snappier?
• Architecture: do we want to truly commit to making a monorepo of per-component packages? Or produce a single-package component library?

Once those decisions are made and the repo is in place we should move the existing code from wc-gocam-viz and wc-ribbon into it and retire those individual repos. As part of that code moving we could also consider whether we want to standardize the naming of our components (what is the benefit of a wc- prefix as opposed to something more identifying like go- or geneontology-?)

[pkalita-lbl]

I needed create this issue in some repository so I somewhat arbitrarily chose wc-gocam-viz. The real work is going to happen -- as the title suggests -- in a repo that doesn't exist yet. I'll transfer this issue to the new repo when it exists, if that makes sense.