Add check Uniform Versioning Validation

[mikeharder]

• Pipeline uses GH Action
• Tool is clone of TypeSpecValidation
• Rules
  • Verify default $(tag) exists
  • Add more rules we can think of now, or as we find more bugs in specs
• Support suppressions.yaml
• Run on PRs to give clear guidance how to fix readme.md
• Run on all specs in main
  • If only a few failures, add suppressions then enable pipeline "ReadmeValidation - All"

Notes from @konrad-jamrozik

A quickstart guide I wrote for creating such checks is here:

• Integrate Armstrong Validation into the spec PR check suite. #28773 (comment)

Closely related to:

• Develop semantic model of specs repo dir structure azure-sdk-tools#8203

[konrad-jamrozik]

Avocado was in effect our "README validation" check before. There is bunch of work related to it:

• https://github.com/Azure/azure-sdk-tools/issues?q=is%3Aopen+is%3Aissue+Avocado
• https://github.com/Azure/avocado/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc

The README validation ideally should build directly on this work (once ready):

• Develop semantic model of specs repo dir structure azure-sdk-tools#8203

For suppressions, we probably should also support the README.md suppressions and sdk-suppressions.yaml:

• Documentation: Spec PR tools suppressions mechanisms reference azure-sdk-tools#8133

[konrad-jamrozik]

I had a chat with @mikeharder. We are considering introducing a check named Uniform Versioning Validation. It would take care of directory structure validation and README.md validation, ensuring, among others, that they follow the uniform versioning principles as outlined in this PR:

• Update directory-structure.md: clarify service, service group, uniform versioning. #28929

[konrad-jamrozik]

A related work that will require understanding spec dir structure is checking if a PR is an "incremental TypeSpec" PR:

• [PR Workflow] Automatic ARM sign-off for TypeSpec-based PRs  azure-sdk-tools#7352 (comment)

[konrad-jamrozik]

Some desired checks from @josefree :

For "uniform versioning", it would be great if there could be automatic check, and pop-up error in spec PR pipeline. For example,

• The service version ❗must❗ be always represented in its entirety; any SDK or documentation referring to the service must encompass all of it.

and

• stable and preview API versions ❗cannot❗ have the same date.
• Moving to stable from preview by removing -preview suffix is ❗not allowed❗.