fix: use scopes_supported in OAuth server metadata

[xiaoyijun]

According to the RFC, the supported scopes filed name should be scopes_supported rather than scope_supported.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

[Copilot]

Pull Request Overview

This PR aligns the OAuth metadata field name with RFC8414 by replacing scope_supported with scopes_supported.

• Renamed scope_supported to scopes_supported in the metadata model and updated its docstring.
• Updated existing tests to check scopes_supported instead of the old field.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
tests/utils/fetch_server_config_test.py	Added assertions for the new scopes_supported field
mcpauth/config.py	Renamed attribute and added RFC link in its docstring

Comments suppressed due to low confidence (2)

mcpauth/config.py:141

• Consider adding a fallback for servers that still emit the older scope_supported key (e.g., via Pydantic's Field(alias='scope_supported', alias_priority=2)) to maintain broader interoperability.

    scopes_supported: Optional[List[str]] = None

mcpauth/config.py:143

• [nitpick] Attribute-level docstrings aren't picked up by many tools; consider using Field(..., description="...") so the description becomes part of the Pydantic model schema and generated docs.

    JSON array containing a list of the OAuth 2.0 `scope` values that this authorization