### What do you see as an issue?

The `--state` CLI flag on `airflow dags list-jobs` does not tell the user what arguments it can take.

https://github.com/apache/airflow/blob/1bd538be8c5b134643a6c5eddd06f70e6f0db2e7/airflow/cli/cli_config.py#L280

It probably needs some keyword args similar to the following:

```python
 metavar="(table, json, yaml, plain)",
 choices=("table", "json", "yaml", "plain"),
```

### Solving the problem

The problem can be solved by adding those keyword arguments so that the user gets a suggestion for what state arguments can be passed in.

### Anything else

Any suggestions on what can be a valid state would be much appreciated. Otherwise, I'll find some time to read through the code and/or docs and figure it out.

### Are you willing to submit PR?

- [X] Yes I am willing to submit a PR!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)

"examples:\n"
            "To check if the local scheduler is still working properly, run:\n"
            "\n"
            '    $ airflow jobs check --job-type SchedulerJob --local"\n'
            "\n"
            "To check if any scheduler is running when you are using high availability, run:\n"
            "\n"
            "    $ airflow jobs check --job-type SchedulerJob --allow-multiple --limit 100"
        ),
    ),
)
core_commands: list[CLICommand] = [
    GroupCommand(
        name="dags",
        help="Manage DAGs",
        subcommands=DAGS_COMMANDS,
    ),
    GroupCommand(
        name="kubernetes", help="Tools to help run the KubernetesExecutor", subcommands=KUBERNETES_COMMANDS
    ),
    GroupCommand(
        name="tasks",
        help="Manage tasks",
        subcommands=TASKS_COMMANDS,
    ),
    GroupCommand(
        name="pools",
        help="Manage pools",
        subcommands=POOLS_COMMANDS,
    ),