Update events-that-trigger-workflows.md

[mcummings128]

Why:

Closes: #43081

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

workflow_dispatch is absolutely able to be triggered when the workflow file is not in the default branch. The issue lies in HOW it can be triggered: when it is in the default branch, the Github UI can be used. When it is not, then the Github UI cannot be used. The "Note" regarding this should be updated, as it misleads the reader into thinking that workflow_dispatch is more limited than it is.

Please also refer to the Issue linked above.

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.19 3.18 3.17 3.16 3.15 3.14	fpt ghec ghes@ 3.19 3.18 3.17 3.16 3.15 3.14

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

🤖 This comment is automatically generated.