[SDK ask] TypeSpec Brownfield Conversion - To prevent partial conversion when a service or a service group under a root spec folder submit typespec for review

[josefree]

SDK do not support to release upon mixed TypeSpec and Swagger, nor multiple API versions. Therefore, in the following two scenarios, we expect validation tool can detect and pop up error to stop service partner submit typespec for only part of service APIs defined in previous versions using swagger.

• when a service of service group (API specs of multiple services are under the same root spec folder, or for management plane, under the same ARM namespace folder) submit typespecs for review, the validation can detect if the typespecs do not cover service APIs of the whole service group. The rest of API specs stay using swagger. An example pull request was https://github.com/Azure/azure-rest-api-specs/pull/28620/files.
• when a service submit typespecs for only part of service APIs (or resource types & operations) defined in previous version using swagger. the rest of API specs stay using swagger.

Usually, these scenarios are with brownfield conversion. The feature should be enabled prior to the program of TypeSpec Brownfields Conversion in execution.

[konrad-jamrozik]

@mikeharder I am assigning you and myself. @MattGertz FYI.

[josefree]

cc @raych1