[eslint-plugin] should ts-name-options rule allows OperationOptions?

[jeremymeng]

Current API design guidelines require that method options bag type name should be <MethodName>Options

https://azure.github.io/azure-sdk/typescript_design.html#ts-options

However, in many cases, those methods only need a OperationOptions without any further customizations. Should we allow this special case?

[xirzec]

Allowing OperationOptions directly feels like a reasonable exception here; we're not minting a new type with a bad name (which is what the rule exists to prevent) and it won't hurt anything if consumers continue to use that type after we implement operation-specific options that extend OperationOptions