Method renames for dotnet automation API GA

[t0yv0]

Takes care of the part of #6459 as relates to method renames. In addition renames RemoveConfigAsync and RemoveAllConfigAsync.

[t0yv0]

CC @orionstudt

[orionstudt]

I will say that I'm not a fan of these names... I had thought that in the original Automation API PR we had agreed to go with names that unify related methods alphabetically for intellisense and usage purposes here

[t0yv0]

Thanks for that pointer @orionstudt and the feedback. I think the current priority is cross-SDK consistency of the operation names so the decision was made to got his way. I will take a note to bring this up again with the team so we may reconsider. Especially since consistency can be solved the other way, that is editing the other SDKs.

[komalali]

@orionstudt Ah, I definitely missed that entire conversation.

The issues for the other languages were never opened, and I wasn't aware that we had decided that we would align the other languages with C# rather than the other way around.

At this point, it wouldn't be entirely painless to take this breaking change in the 3 other SDKs, not to mention the related changes in the code that consumes these APIs. If we were to do it, we need to somehow fit that into the next 12 days which I'm not sure we have the capacity for.

[orionstudt]

@komalali it is what it is! I don't think it is that big of an issue, but I do think there is value in related methods being near each other alphabetically for intellisense. I think I tried to clarify the miscommunication here but I failed to be specific enough or open the other issues so its on me 😅