feat(reviews): implement cache revalidation for reviews after submission

[matthewvolk]

What/Why?

Testing

Migration

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0e82120

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
catalyst-b2b	Ready	Preview	Comment	Nov 14, 2025 4:38pm
catalyst-canary	Ready	Preview	Comment	Nov 14, 2025 4:38pm

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
catalyst	Ignored			Nov 14, 2025 4:38pm

[matthewvolk]

Unsure if this is the best approach

[matthewvolk]

I'm trying to poke holes in this approach... since we don't have reCAPTCHA on the form... does this approach leave the merchant open to bots spamming their reviews and reviews data effectively never being cached?