[Release Prep]: Update proposed changelog

[github-actions]

Automated and continuously updated PR for adding changeset entries for merged PRs.

TODO

• Determine patch/minor/major impact for each package for each changeset
• if applicable, mark/remove certain changes as omitted from the changelog
• if applicable, bundle changes together in to a single "change set"

Remember

• This PR is updated on every merge to main
• This PR is force-pushed, so changes should happen on a separate branch

[NullVoxPopuli]

TODOs for myself w/r/t this automation:

• add flag to the tool (and use it in the package.json) to only include changes that belong to packages
• figure out what happened here (too many packages detected as changed)

Once those two things are dealt with,

• open a PR to embroider, upgrading the dep

[ef4]

1. Why --only-prs?

2. How did you decide what to put in .changeset/.recoverignore? Because I'm seeing stuff in there that's definitely publicly-facing changes.

[NullVoxPopuli]

Why --only-prs?

It's the only way to get a PR link to GitHub, specifically for attributing work and grabbing the title of the change as well.

How did you decide what to put in .changeset/.recoverignore?

generally things that didn't fit in to any packages (such as .github/ changes)
that said the "what packages changed detection" isn't perfect -- though, I've (so far) only noticed it saying too many packages changed, rather than too few. Need to do another pass on that

Ideally, when that's figured out, a --only-packages flag would mean that we wouldn't need a .recoverignore and the detected changed packages would be more correct (today, a change in one package can flag a change in all packages -- but it's just git diffing, so.. need to look in to that)