Document description, default and options for workflow_dispatch inputs

[kburym]

Fixes #46299

The on.workflow_dispatch.inputs.<input_id> section documented only required and type. This adds sections for description, default and options, matching the workflow schema in actions/languageservices (workflow-parser/src/workflow-v1.0.json, at fb5c6e4) and the example already on the page. options is noted as applying only to choice inputs.

[github-actions]

Please don't raise pull requests against an existing issue that another user has raised until it's been marked with a help wanted label. We need to properly assess all issues before we can accept community contributions, and determine whether it's something we need to fix internally, or how many articles are affected and what the scope of the fix will be. For now, we're going to close this pull request.

[github-actions]

Thanks for submitting a PR to the GitHub Docs project!

In order to review and merge PRs most efficiently, we require that all PRs grant maintainer edit access before we review them. For information on how to do this, see the documentation.

[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.22 3.21 3.20 3.19 3.18	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18

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

🤖 This comment is automatically generated.

[subatoi]

Apologies as this shouldn't have been closed, since it relates to your own issue. We'll review this as a new issue/PR pairing and the appropriate team will comment as soon as possible