Handle C# SDK Naming Requirements for Autogenerated Specs

[hmmorales]

SDK configuration pull request

Purpose of this PR

• Make changes to the SDK configuration only when there are no modifications to the API specification, eliminating the need for an ARM or Stewardship Board API review.

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

• I confirm this PR is modifying only SDK configurations, and not API related specifications.
• I have reviewed and used the respective tspconfig.yaml templates:
  • ARM tspconfig template
  • Data plane tspconfig template

Getting help

• First, carefully read through this PR description, from top to bottom. Fill out the Purpose of this PR and Due diligence checklist.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure and https://aka.ms/ci-fix.
• If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
  This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

[openapi-pipeline-app]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ Your PR has breaking changes in the generated SDK for Go (label: BreakingChange-Go-Sdk). Refer to step 3 in the PR workflow diagram.
• ❌ Your PR has breaking changes in the generated SDK for JavaScript (label: BreakingChange-JavaScript-Sdk). Refer to step 3 in the PR workflow diagram.
• ❌ Your PR has breaking changes in the generated SDK for Python (label: BreakingChange-Python-Sdk). Refer to step 3 in the PR workflow diagram.
• ❌ The required check named Automated merging requirements met has failed. This is the final check that must pass. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide. In addition, refer to step 4 in the PR workflow diagram

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/iotoperations/armiotoperations	There is no API change compared with the previous version
Java	azure-resourcemanager-iotoperations	There is no API change compared with the previous version
Python	azure-mgmt-iotoperations	https://apiview.dev/Assemblies/Review/769883b1547944f0b54d7e35ce415ee3?revisionId=7fc75957482145ceb36deb2b4b3f20fa
JavaScript	@azure/arm-iotoperations	https://apiview.dev/Assemblies/Review/3497f183f9b842898633d9bc7bf2541d?revisionId=e4b7a9dabb1849cb957b139fae02d3b3
TypeSpec	IoTOperations.Management	https://apiview.dev/Assemblies/Review/0453fd959bbc4dbb9ee5a6266fb1ce29?revisionId=55460027afa9451599cb0e3686300ec2

[azure-sdk]

API change check

APIView has identified API level changes in this PR and created following API reviews.

Microsoft.IoTOperations

[hmmorales]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 4 pipeline(s).

[hmmorales]

Adding this issue for tracking: Azure/azure-sdk-for-net#45949

[live1206]

This workaround is not needed anymore, generator can remove the list operation properly.

[live1206]

Ignore the azure-sdk-for-net-track2 failure for the current PR merge, we will handle it with custom code during .NET SDK generation in azure-sdk-for-net.

[chgennar]

I don't think Config is the right substitute here. What about DataflowAction?