Consider adding switch to opt out of options type name disambiguation

For `FooClient`, all client/client method options will have the prefix `FooClient`. This is to disambiguate the case when an SDK contains multiple clients and two (or more) clients have a method with the same name (e.g. `SomeMethod`), Without the prefix, `SomeMethodOptions` would collide.

For SDKs with a single client, and that will _always_ have a single client, the prefix is unnecessary and creates ugly names. We could consider adding a switch to opt out of this prefix. It works IFF an SDK contains a single client, else an error is generated (this is what we do in the go emitter). Note that opting in and then later opting out would result in a breaking change. So, one must be 100% confident that the SDK in question will always contain only one client.

Commencez par examiner le comportement de nommage des types d’options de l’émetteur Rust et comparez-le à la gestion d’un client unique par l’émetteur Go. Définissez où doit se trouver le commutateur de désactivation, comment plusieurs clients doivent produire une erreur, et vérifiez que les SDK à client unique omettent le préfixe du client sans modifier le comportement par défaut.

Rédigé par le modèle d'indexation à partir du texte de l'issue.