remove double "operations" in operation group names

[iscai-msft]

In the case of "DeploymentOperationsOperations", we should only have one Operations.

Don't really believe this is breaking, treating it more like a bug fix. This only impacts the class name of the operation group (which is technically public, but users shouldn't instantiate them), and the filename that this operation group is stored in (which is private). The operation group property on the service client stays the same

[iscai-msft]

Decided not to make this fix after talking to Laurent Mazuel (@lmazuel) . Reasons are:

1. users should never care about the operation group class name. They should only interact with the attributes on the service client, whose name is currently correct, so this change doesn't add any customer value.
2. This could cause errors when there didn't use to be any. Say, if a swagger defines operation groups Deployment and DeploymentOperations. Now, we create both operation groups with the same name, which will cause issues.

Thus, we're not making this change because there's not any customer improvement, and it opens us up to potential issues in the future