Naming mismatch between options/arguments and handler parameters is non-obvious

System.CommandLine's most common usability issue is that handler parameters whose name doesn't match an option or argument will never be successfully bound at invocation time.

For example, it may seem intuitive that the following should work, but handler parameter `i` will never be bound:

```cs
var command = new RootCommand
{
new Option("--an-int")
};

command.Handler = CommandHandler.Create( i => /* */ );
```

The alternative APIs were introduced here:

* #1012

A more flexible approach (using a similar API pattern but generating the handlers using source generators) is being worked out here:

* #1362

Possible approaches include:

* ~Add an ordering-based matching strategy. This possibly suffers from other non-obviousness problems. Maybe the two strategies can operate together.~
* ~Add an error checking mechanism. Ideally this would not be a runtime check since, once compiled, it would be a continual performance hit while the answer would never change. An analyzer might be a good approach.~

Beginne damit, das in diesem Issue beschriebene Verhalten bei der Bindung von Handler-Parametern und die in #1012 und #1362 diskutierten alternativen APIs zu prüfen. Das Issue nennt keine Dateien, Tests oder abgestimmte Vorgehensweise; Umfang und Verifizierungskriterien müssten vor der Implementierung mit den Maintainer:innen abgestimmt werden.

Vom Indexierungsmodell aus dem Issue-Text verfasst.