Reopen Tests ARM, test case for listing available operations

[v-hongli1]

• ARM, test case for listing available operations #688

Cadl Ranch Contribution Checklist:

• I have written a scenario spec
• I have meaningful @scenario names. Someone can look at the list of scenarios and understand what I'm covering.
• I have written a mock API
• I have used @scenarioDocs for extra scenario description and to tell people how to pass my mock api check.

[XiaofeiCao]

Please ensure generated Java code can pass the test.

[XiaofeiCao]

Let's put this into a new folder.
http/azure/resource-manager/operations:

• main.tsp
• available-operations.tsp
• check-name-availability.tsp

Reason is that these two operations are not tied to any particular resource, rather RP itself.

[v-hongli1]

@XiaofeiCao

Let's put this into a new folder. http/azure/resource-manager/operations:

• main.tsp
• available-operations.tsp
• check-name-availability.tsp

Reason is that these two operations are not tied to any particular resource, rather RP itself.

Is the namespace defined as Azure.ResourceManager.Operations? However, this naming will cause an exception like Duplicate name: "Operations".

[XiaofeiCao]

Your namespace and interface name collide with each other(they are all called Operations).

I see, there is also a Azure.ResourceManager.Operations interface in arm lib...
We should rename the namespace to something else, candidates:

1. Azure.ResourceManager.CommonOperations
2. Azure.ResourceManager.ArmOperations
3. Azure.ResourceManager.OperationTemplates

In the future, we will also have LRO, pageable, and other operations that need deeper testing.
I would prefer option3, Azure.ResourceManager.OperationTemplates. Chances that we define raw operations for ARM
is pretty low..
@iscai-msft Let me know your thoughts, thanks!