Update default packages in example project

[ChrisWiegman]

Tasks

• [x] I have signed a Contributor License Agreement (CLA) with WP Engine.
• [x] If a code change, I have written testing instructions that the whole team & outside contributors can understand.
• [x] I have written and included a comprehensive changeset to properly document the changes I've made.

Description

Updates safe packages in the getting started example excluding Next >12.x, React (and related) > 17.x and WordPress Block Library > 7.x

Related Issue(s):

1856

Testing

Default tests should be sufficient without further changes.

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 1780ec0eb83da81f144eddfa434498a9cdb73202

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

[github-actions[bot]]

📦 Next.js Bundle Analysis for @faustwp/getting-started-example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

⚠️ Global Bundle Size Increased

Page	Size (compressed)
global	250.44 KB (🟡 +3.66 KB)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Three Pages Changed Size

The following pages changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load	% of Budget (350 KB)
/[...wordpressNode]	302 B	250.74 KB	71.64% (+/- <0.01%)
/example	851 B	251.27 KB	71.79% (+/- <0.01%)
/preview	282 B	250.72 KB	71.63% (+/- <0.01%)

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.