chore: Exclude "next" branch from GH workflows

[ahuseyn]

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

The next branch is an experimental branch for the ongoing work on the new Faust. To prevent unnecessary warnings and reduce CI resource usage, we need to disable workflows on this branch.

Related Issue(s):

• Disable GitHub workflows for next branch #2161

Testing

Screenshots

Documentation Changes

Dependant PRs

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1c9a5d8

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]

📦 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! 🙌