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.

首先检查 Rust emitter 的选项类型命名行为，并将其与 Go emitter 对单个 client 的处理进行比较。确定 opt-out switch 应放置在哪里、多个 client 应如何产生错误，并验证单 client SDK 会省略 client 前缀，同时不改变默认行为。

由索引模型根据 Issue 内容生成。