[FEATURE] Support for Protected Resource Metadata Discovery Requirements

# Feature

Support for Protected Resource Metadata Discovery Requirements [1]. If the tool returns an HTTP 401 Unauthorized response, for example:

```
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer resource_metadata="https://mcp.example.com/.well-known/oauth-protected-resource",
scope="files:read"
```
The MCP client should follow the Authorization Server Metadata Discovery process [2] to retrieve the resource_metadata, and then redirect to the Identity Provider to initiate the step-up process.

Currently, a 401 error is shown in the MCP JAM console.

[1] https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization#protected-resource-metadata-discovery-requirements
[2] https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization#authorization-server-metadata-discovery