chore: yet another follow up for changesets release

[krizzu]

Summary

Couple of things:

• I still have no idea why GH action is picking gh bot as git credentials (it works fine in a fork), so I'm using variables now for name and email for the bot
• I've noticed during my tests that README would be mixed up by changeset, so I applied changes
• Also I've noticed that one of our releases has not been pushed to npm, so added a warning for it in README
• I've added api and sqlite-storage to ignore, to avoid changesets releasing it for now (not ready yet)

[changeset-bot]

⚠️ No Changeset found

Latest commit: e735913

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR