[core-http] sendOperationRequest needs an overload that takes OperationOptions

[bterlson]

Presently the utility method OperationOptionsToRequestOptionsBase must be applied before calling into sendOperationRequest. This should not be necessary.

[xirzec]

As far as I can tell, sendOperationRequest is a generated method inside the ServiceClients, so the fix here would be to modify the autorest codegen.

@daviwil @joheredi - is this covered by the next-gen autorest work?

[jeremymeng]

I may be wrong but generated files seem to just import ServiceClient from corehttp

[xirzec]

@jeremymeng nah, you're right, I got tricked by VS Code and go to definition. this.sendOperationRequest comes from core-http's ServiceClient, but I didn't notice we were using inheritance for it.

OK this bug is now actionable again.

[xirzec]

@jeremymeng OK what I was actually thinking about. The generated method signatures all take an options bag that extends from coreHttp.RequestOptionsBase - which I guess technically can be anything since it has a string index property on it.

I guess the ask in this issue is that we cheat and let that string indexer allow us to pass OperationOptions wholesale and then structurally recognize it on the other side.

[xirzec]

This was done in core-client as part of #9854