TCGC decorator `@clientLocation` might break the resource detection logic

[ArcturusZhang]

Recently we added a feature that we would only mark a thing as resource when its interface has the @armResourceOperations decorator (PR).
The @clientLocation decorator from TCGC allows TCGC to create new clients for operation for client side reorganization.
When we reorganize resource operations, the new created clients will never have @armResourceOperations and this would break our detection rule for resources.

Currently we have to introduce workarounds to fix this, by adding the !csharp scope to all such occurrence of decorators to ensure the resource detection.
One of the side effect of this workaround is that this breaks the operationId building logic in TCGC, which changes the operationId displayed in our xml doc of operations, and also breaks the mechanism of finding corresponding example files.

[ArcturusZhang]

We might not fix that here, but we are looking forward to the new generator fixing this.