docs: clarify forked pull request token wording

[hiromieguchi802-lab]

Summary

• clarify that the write-token downgrade applies to forked pull request events except pull_request_target
• avoid implying that pull_request_target is subject to the same read-only adjustment

Fixes #32398.

Testing

• ran npm run lint-content -- --precommit --paths content/actions/reference/workflows-and-actions/workflow-syntax.md

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[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/workflow-syntax.md	fpt ghec ghes@ 3.20 3.19 3.18 3.17 3.16 3.15 3.14	fpt ghec ghes@ 3.20 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.

[Sharra-writes]

@hiromieguchi802-lab This looks right to me based on the issue, so I'll give it approval. We are (still) in a deploy freeze, though, so I can't merge yet. Not sure when it's going to end, or I would give you a timeframe.