Update push event: Mention it can trigger non-default branch workflows

[mcummings128]

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Regarding the push event behavior, adds a note that workflows not merged to the default branch can be triggered by push events. This is useful to call out specifically because there will be times when users need to test a workflow but cannot merge it to the default branch for whatever reason. Having this in official documentation helps users have a reputable, citable source regarding how to trigger a workflow without merging into the default branch--methods to do so are not explicitly mentioned in any documentation I've come across

This doesn't have to be in NOTE format specifically, but the content should be there.

See the documentation

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
actions/reference/workflows-and-actions/events-that-trigger-workflows.md	fpt ghec ghes@ 3.21 3.20 3.19 3.18 3.17 3.16	fpt ghec ghes@ 3.21 3.20 3.19 3.18 3.17 3.16

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

@mcummings128 We actually already have information about this here: https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#running-your-workflow-only-when-a-push-to-specific-branches-occurs

The Actions team would rather link to what we already have than duplicate it here, and I agree. If you want to add a, "For more information about (explain thing here, I don't know that I can summarize accurately), see [AUTOTITLE](actions/reference/workflows-and-actions/events-that-trigger-workflows#running-your-workflow-only-when-a-push-to-specific-branches-occurs)," that would be fine.