Preserve OAuth resource path during scope discovery

[blakewang-atlassian]

Summary

• Preserve the full MCP server URL when discovering OAuth protected resource metadata
• Add a regression test for path-based MCP endpoints such as /v1/mcp/preview

Why

Some MCP servers expose different protected resource metadata per path. Discovering metadata from the origin URL drops the endpoint path and can cause Inspector to request scopes for the wrong resource.

Test plan

• npm test -- --runTestsByPath src/lib/hooks/tests/useConnection.test.tsx
• npx prettier --check client/src/lib/hooks/useConnection.ts client/src/lib/hooks/tests/useConnection.test.tsx
• git diff --check

[cliffhall]

Closing: v1 is deprecated.

Thank you for this contribution, and apologies for the long wait for a response.

v1 will receive security fixes only. We reviewed every open v1 PR for security impact before closing — see the backlog triage in #1819 — and a small number were retained for a final 1.0.5 patch release. This one is a functionality, compatibility, or cleanup change rather than a vulnerability fix, so it is being closed unmerged. This is not a judgment on the quality of the work — it's a consequence of the branch it targets being frozen.

If the underlying problem still exists in v2, we'd genuinely like to know. Please open an issue describing it against v2. Note that we accept external contributions as issues rather than pull requests — maintainers handle design and implementation through a prompt-driven workflow. See CONTRIBUTORS.md.

Thanks again for taking the time to contribute to the Inspector.