Faust deprecation notices

[blakewilson]

Tasks

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

Description

Adds deprecation notices to @faustjs/core, @faustjs/react, and @faustjs/next legacy packages. These can be observed here:

• https://github.com/wpengine/faustjs/tree/faust-deprecation-notices/packages/core
• https://github.com/wpengine/faustjs/tree/faust-deprecation-notices/packages/react
• https://github.com/wpengine/faustjs/tree/faust-deprecation-notices/packages/next

This PR also makes the legacy.faustjs.org banner more clean that Faust.js (GQty) has been deprecated and when support will end. This can be tested and observed by checking out this branch, cd internal/legacy.faustjs.org, npm install, then npm run dev

Once these changes have been merged and a new release is cut, we'll finally want to deprecate these three packages within NPM: https://docs.npmjs.com/cli/v8/commands/npm-deprecate

This makes it clear from the NPM website as well as CLI that a deprecated package is being installed.

Related Issue(s):

Testing

Screenshots

Documentation Changes

Dependant PRs

[changeset-bot]

🦋 Changeset detected

Latest commit: cde880b

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@faustjs/react	Patch
@faustjs/core	Patch
@faustjs/next	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

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

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

This PR introduced no changes to the JavaScript bundle! 🙌