Conformance testing: add auth conformance testing

[Kehrlann]

Conformance testing for the auth suite.

Motivation and Context

See MCP Conformance repo.

How Has This Been Tested?

Self-testing.

Breaking Changes

n/a

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

To fix the problem, the workflow should explicitly declare restricted GITHUB_TOKEN permissions instead of inheriting the repository default. Since this workflow only checks out code, sets up Java, builds with Maven, and runs conformance tests, it only needs read access to repository contents (and possibly to packages if they are pulled, though none are explicitly shown).

The best minimal fix without changing functionality is to add a root-level permissions block right under the name: and on: keys so that it applies to all jobs that do not override it. A conservative and commonly recommended baseline is:

permissions:
  contents: read

This grants read-only access to repository contents, which is required by actions/checkout and is sufficient for the rest of the steps as written. No other scopes (issues, pull-requests, actions, etc.) are needed based on the shown YAML. Concretely, in .github/workflows/conformance.yml, add the permissions mapping after the on: block (or directly after name: if you prefer) and before jobs:. No imports or additional definitions are needed, since this is pure workflow configuration.

[tzolov]

Thanks @Kehrlann

[chemicL]

👏 🚀