chore: add auto-deployment via Changesets

[MichaelDeBoey]

See @chaance's remix-run#9 & @mcansh's remix-run#16

---

#101 needs to be merged first

[Gozala]

Hy @MichaelDeBoey I don't have anything against Changesets, but I also have no experience using it. I'm hesitant to switch from release-please to Changesets unless there is a compiling reason for it as adopting it would take up already scarce time I have available for this project.

That said if you do have a compelling case please point those out so they could be considered.

[MichaelDeBoey]

@Gozala We use changesets in the Remix repos, so both @jacob-ebey & I are used to it

One of the main benefits of changesets is that you can create a whole custom explanation for your release notes as part of your PR, which is something that's not possible with release-please
Another benefit is that it automatically updates the version numbers of nested dependencies (so if blob updates, the version number of blob will be changed in all other package.jsons)

This PR also adds some nice things like manypkg to help with monorepo best practices

[MichaelDeBoey]

@Gozala Is there anything else you want me to do before we can merge this one?

[jacob-ebey]

Release please is the shit and if I had my way Remix would release with it. Don't let our release process influence how you manage this project.

[Copilot]

Copilot reviewed 8 out of 15 changed files in this pull request and generated 1 comment.

Files not reviewed (7)

• .changeset/config.json: Language not supported
• package.json: Language not supported
• packages/blob/package.json: Language not supported
• packages/fetch/package.json: Language not supported
• packages/file/package.json: Language not supported
• packages/form-data/package.json: Language not supported
• packages/stream/package.json: Language not supported