[Se] Validate and enhance linter engines for TypeSpec conversion rules

### Context

The TypeSpec team has a [plan for converting existing Azure services to TypeSpec](https://microsoft-my.sharepoint.com/:w:/g/personal/mattge_microsoft_com1/ER3nulfpzGxErW2woxS2KMEB6lNwzBe4CzM7FVQkHdK7-A?e=0WswMD). The process involves manual refinement of TypeSpec files (TSPs), validation through human reviews, and various work items assigned to different teams for approval and automation. The primary goal is to ensure that the converted TypeSpec generates an OpenAPI specification functionally equivalent to the original, maintaining round-trip correctness.

### Description

EngSys must validate that the linter engines can support the required automation rules for the conversion process. The Engineering Systems (EngSys) team is responsible for ensuring that the linter engines and other automation tools are capable of supporting the rules set by ARM and the API Stewardship Committee. This involves validating and possibly enhancing the existing automation framework to handle the new requirements for TypeSpec conversions. Ensuring that the linter engines are up to the task is crucial for maintaining the quality and consistency of the converted services.