chore: Upgrade to @ariakit/react v0.3.14

[gnapse]

Short description

Upgrades to the latest Ariakit. Ariakit underwent a relatively major API change, a breaking change. However, given how we encapsulate their API within ours, I suspect that it is not a breaking change for us (to be determined).

PR Checklist

• Added tests for bugs / new features
• Updated docs (storybooks, readme)
• Executed npm run validate and made sure no errors / warnings were shown
• Described changes in CHANGELOG.md
• Bumped version in package.json and package-lock.json (npm --no-git-tag-version version <major|minor|patch>) ref
• Updated all static build artifacts (npm run build-all)
• Reviewed and approved Chromatic visual regression tests in CI

Versioning

We're releasing this as a beta version, so that we can dip our toes into upgrading in the apps. The apps not only use Reactist, but in many cases use other Ariakit components directly. So when upgrading the apps to the new Reactist version, we need to also upgrade the apps to use the new Ariakit version directly.

[frankieyan]

Tested all the updated components in storybook and they look good. I would suggest releasing this as a new major version for the reason you listed so that dependabot/renovate doesn't update this automatically.

If we run a parallel beta version instead, how long do you think we should keep it around for?

[frankieyan]

This is from https://github.com/ariakit/ariakit/blob/78b86daec880719625380492b711816457559efa/packages/ariakit-react-core/src/utils/hooks.ts#L126 right? Is there someway to attribute it back to them?

[frankieyan]

@gnapse my weekly bug requires the Ariakit upgrade here, should I take over this PR from you?

[gnapse]

@Bloomca I've noticed that you have work that depends on this. Let me know if you need help, as I should've been on top of this before, instead of neglecting it for some time. I can consider resuming the work here myself.

[Bloomca]

Sorry I made several releases due to another library depending on the Reactist, but I haven't realized it depends on ^22.0.0, and not just any 22 version.