refactor: Unify IoTOperations folder structure per Azure Guidelines

[qiaozha]

• Moved TypeSpec files from IoTOperations.Management/ to resource-manager/Microsoft.IoTOperations/IoTOperations/
• Unified TypeSpec and swagger files under the same service folder structure
• Updated tspconfig.yaml with correct emitter output directory and ARM types configuration
• Fixed all input-file references in readme.md to use correct relative paths
• Added suppressions.yaml for TypeSpecRequirement to handle legacy swagger versions
• Ensured compliance with Azure REST API specification folder structure guidelines

The new structure follows the pattern:
specification/iotoperations/resource-manager/Microsoft.IoTOperations/IoTOperations/ ├── *.tsp (TypeSpec files)
├── tspconfig.yaml
├── readme.md
├── suppressions.yaml
├── examples/ (TypeSpec examples)
├── models/ (TypeSpec models)
├── preview/ (preview swagger versions)
└── stable/ (stable swagger versions)

Choose a PR Template

Switch to "Preview" on this description then select one of the choices below.

Click here to open a PR for a Data Plane API.

Click here to open a PR for a Control Plane (ARM) API.

Click here to open a PR for only SDK configuration.

[openapi-pipeline-app]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
• ❌ 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]

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

[github-actions]

API Change Check

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

Language	API Review for Package
Swagger	Microsoft.IoTOperations-IoTOperations
TypeSpec	Microsoft.IoTOperations
Go	sdk/resourcemanager/iotoperations/armiotoperations
Java	com.azure.resourcemanager:azure-resourcemanager-iotoperations
JavaScript	@azure/arm-iotoperations
Python	azure-mgmt-iotoperations

[live1206]

The .NET SDK validation failure is due to a known issue for .NET SDK generation: Azure/azure-sdk-for-net#45949. We have a mechanism to flatten a single property out if the model only contains 1 property, and it doesn't work properly for multiple layers of flatten. We can ignore this for now, we can fix it with custom code in sdk repo. Due to code freeze in autorest.csharp, we are about to deprecate it, we will fix this in the new generator instead.

[github-actions]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ The suppressions added to the AutoRest config files (README.mds) require review. Refer to step 1 in the PR workflow diagram, or to step 3, depending on the kind of suppression you did.

Important checks have failed. As of today they are not blocking this PR, but in near future they may.
Addressing the following failures is highly recommended:

• ⚠️ The check named SDK Validation Status has failed. 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

Comment generated by summarize-checks workflow run.