chore: prepare for first stable release

[tomasciccola]

should close #752
Additionally we are:

• changing the package name to @comapeo/core

We could also:

• Edit readme to reflect current state of the project (I wouldn't lose much time on this now, just maybe removing the Early development disclaimer and correct npm command)
• Edit authors? We can point different authors (probably can automate this so it reflects commits authors) or just put "Awana Digital" (simpler but hides individual authors)

This PR is also made so that we can test OPTICS for releasing a stable version.
We should have an NPM_TOKEN on the project before merging the OPTICS_RELEASE so we can actually publish the package.

On the other hand, I'm wondering if PRs merged after this, would be included in the release (I think yes?), but if not, we should make sure we're not missing anything (I think not)

[EvanHahn]

LGTM.

• Could you add an issue to update the readme? (Or just update it if that's faster.)
• I'll clean up Authors right now.
• Could you make sure CHANGELOG.md is ready to go? I think we probably just want to delete it entirely.

[EvanHahn]

Actually, could you run npm install before merging? I think that will update package-lock.json.

[tomasciccola]

This needs first the publishing of mapeo-schema v1 before merging