Enforce unified API versions in RP specs

Implement a tool to detect if any spec "tags" are mixing API versions.

If we name the parts of the path as follows:

```
Microsoft.Monitor/stable/2023-04-03/monitoringAccounts_API.json
///
```

We might want rules like:

* The `` of all files must be the same ("preview" or "stable")
* Within an ``, the of all files must be the same
* If `` is "preview", must end with "-preview". Else, `` must not end with "-preview".
* The `` of all files must match

Questions:

* Are versions required to be aligned across different ``?