new publishing scope and uniform versioning

[bcakmakoglu]

Currently, all packages tied to Vue Flow are published at the @braks scope (which is really just my own tag) but that's not meaningful in the context of Vue Flow.

So I am thinking of renaming the core package (any suggestions for names are welcome) and use a scope like @vueflow for sub-packages, so there's a clear identification what these packages belong to.
Or put everything into the @vueflow scope.

I'll add some name suggestions in here:

• vue-flow (is sadly taken but I will try to contact the current owner, as the package doesn't appear to be maintained)
• vue-flow-renderer (basically the same as the react-flow version)
• @vueflow/core
• ...

after this planned republish I will probably switch to a uniform semantic versioning, so that if the core is 0.5.0 each sub-package also is 0.5.0 etc.

There's probably gonna be some changes to the CHANGELOG as well.

[bcakmakoglu]

Switch to the new scope/name might be as soon as June / end of June but I will announce it again before switching over so anyone using the old name can migrate without issues 🐶

Though I am considering doing a thorough cleanup of the API and releasing a stable 1.0.0 package instead of staying in beta state. That might take a bit of time (and possibly introduce breaking changes if some duplicate apis get removed like addEdge and addEdges) to make sure no new bugs are introduced and the documentation is updated accordingly.

Anyway, I will keep posting updates in here.