chore: migrate to changesets

[Saadnajmi]

Summary:

nx release has proven to be a bit more cumbersome than we like. I just migrated FluentUI React Native to changesets (microsoft/fluentui-react-native#4003), let's do the same here. We can adopt some of the changes from #2807 , specifically around updating prepublish-check.mjs into an all-in-one script, now named, configure-publish.mts.

Test Plan:

There should be an updated

[changeset-bot]

⚠️ No Changeset found

Latest commit: 578c409

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

[Saadnajmi]

Turns out this is why yarn npm publish skipped a bunch of files.. I would like to upstream this to React Native since it's compatible with npm

[Saadnajmi]

This file is mostly copied from FURN, we probably should adapt the checks to RNMs requirements