[ci] Version packages and generate changelogs with changesets

[douglowder]

Why

In alignment with the move to changesets in expo/expo, we are moving to this model to make releases more reliable and remove the need to manually edit changelogs.

How

• Add changeset dependencies
• Modify release flows and changelog CI
  • Changelog CI will now check for a changeset unless the "no changelog" label is present
  • Hand edits to CHANGELOG.md will now fail the changeset workflow
  • After we merge this, the changeset workflow will be required for merging PRs, except for Dependabot

Test Plan

• CI should pass
• Dry run tests of the release flow
• The new changeset workflow fails for this PR, that is expected (it removes the "main" section at the top of CHANGELOG.md)

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}

[linear-code]

ENG-26500

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.37%. Comparing base (14e14e3) to head (d9693a4).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4580   +/-   ##
=======================================
  Coverage   74.37%   74.37%           
=======================================
  Files        1027     1027           
  Lines       50215    50215           
  Branches    10856    10856           
=======================================
  Hits        37342    37342           
  Misses      11883    11883           
  Partials      990      990           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sjchmiela]

one blocking comment, otherwise looks good. we'll need to release the current changes from main right before merging this pull request

[szdziedzic]

I agree with @sjchmiela comment

[douglowder]

one blocking comment, otherwise looks good. we'll need to release the current changes from main right before merging this pull request

I've addressed the incorrect statement in .changeset/README.md, thanks for the reviews @sjchmiela @szdziedzic ! I'll announce on Slack and do a point release before merging this.

[github-actions]

❌ This PR needs a valid changeset. Run yarn changeset, select the changed packages and the bump type, and commit the new file in .changeset/. Do not edit CHANGELOG.md: the release generates it. The "Validate changesets" step log lists the problems.
⏩ If this PR doesn't require a changelog entry, such as if it's an internal change that doesn't affect the user experience, you can add the "no changelog" label to the PR. The label does not allow edits to CHANGELOG.md files.