Refactor(cognitiveservices): migrate to unified folder structure

[v-xuto]

This PR migrates the cognitiveservices specification to the new unified folder structure according to Azure folder structure guidelines.

Change:

• Consolidated TypeSpec and Swagger files under

cognitiveservices
├── data-plane
│   ├── AnomalyDetector
│   ├── ComputerVision
│   ├── ContentModerator
│   ├── ContentSafety
│   ├── CustomVisionPrediction
│   ├── CustomVisionTraining
│   ├── Face
│   ├── FormRecognizer
│   ├── LanguageAnalyzeConversations
│   ├── LanguageAnalyzeConversationsAuthoring
│   ├── LanguageAnalyzeDocuments
│   ├── LanguageAnalyzeText
│   ├── LanguageAnalyzeTextAuthoring
│   ├── LanguageQuestionAnswering
│   ├── LanguageQuestionAnsweringAuthoring
│   ├── LUISAuthoring
│   ├── LUISRuntime
│   ├── MetricsAdvisor
│   ├── OpenAIAuthoring
│   ├── OpenAIInference
│   ├── Personalizer
│   ├── SpeakerRecognitionIdentification
│   ├── SpeakerRecognitionVerification
│   ├── SpeechBatchAvatar
│   ├── SpeechBatchTextToSpeech
│   ├── SpeechTextToSpeech
│   ├── SpeechToText
│   ├── SpeechVideoTranslation
│   ├── TextAnalytics
│   ├── TranslatorText
│   └── UnifiedVision
└── resource-manager/Microsoft.CognitiveServices/CognitiveServices

• Updated tspconfig.yaml with correct paths and ARM types directory
• Fixed all common-types references and input-file paths in readme.md
• Added suppressions.yaml for legacy API versions
• Verified TypeSpec compilation works correctly
• Updated the relevant paths in specification/suppressions.yaml file
• Updated the relevant paths in cspell.yaml file

Benefits:

• Unified structure for better maintainability
• Aligns with Azure folder structure standards
• Maintains backward compatibility
• Supports future TypeSpec migration efforts

[github-actions]

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).
• ❌ This PR has at least one breaking change (label: BreakingChangeReviewRequired).
  To unblock this PR, follow the process at aka.ms/brch.
• ❌ The required check named Swagger Avocado 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.

[github-actions]

API Change Check

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

Language	API Review for Package
TypeSpec	AnomalyDetector
TypeSpec	ContentSafety
TypeSpec	Azure.OpenAI
TypeSpec	Microsoft.Speech.VideoTranslation
Swagger	AnomalyDetector-ContentSafety
Swagger	Microsoft.CognitiveServices-CognitiveServices
Go	sdk/resourcemanager/cognitiveservices/armcognitiveservices
Java	com.azure.resourcemanager:azure-resourcemanager-cognitiveservicescognitiveservic
JavaScript	@azure-rest/ai-anomaly-detector
JavaScript	@azure-rest/ai-content-safety
JavaScript	@azure/openai
JavaScript	@azure/arm-cognitiveservices
Python	azure-ai-contentsafety
Python	azure-ai-language-conversations-authoring
Python	azure-ai-language-documents
Python	azure-ai-language-questionanswering
Python	azure-ai-language-questionanswering-authoring
Python	azure-mgmt-cognitiveservices