Doc bug in "MCP configuration for Q Developer in the IDE" page

## Problem
In
https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/mcp-ide.html

it says:

_When you use the GUI to add an MCP server to Q Developer in the IDE, the configuration is stored in one of two files:
At the global scope: ~/.aws/amazonq/default.json
At the local scope: .amazonq/default.json_

_However, for legacy reasons, it is also possible to put MCP configuration information in two other locations:
At the global scope: ~/.aws/amazonq/mcp.json
At the local scope: .amazonq/mcp.json_

## Steps to reproduce the issue

I have an older Q installation that upgraded over time, so I had a the 'legacy' `~/.aws/amazonq/mcp.json` file. When I got rid of that file, and used Q Developer in the IDE UI to configure MCP servers, I noticed it reads and writes to a file `~/.aws/amazonq/agents/default.json` (note **agents/** in the path), not `~/.aws/amazonq/default.json`

So, I think the doc above is slightly wrong? Is that correct? It does seem a bit weird that the VS code extension use a config file in `...agents/` but that seems to be the case.

## System details (run `AWS: About` and/or `Amazon Q: About`)

VS Code 1.105.1 , Amazon Q extension v1.102.0, on Mac OS 15.7.1 (24G231)

Start with the MCP configuration for Q Developer in the IDE page at https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/mcp-ide.html and compare its listed paths with the observed ~/.aws/amazonq/agents/default.json behavior. Confirm the correct global and local locations, then update the page so its configuration-path guidance matches the extension; the issue is done when the documented paths are accurate.

Written by the indexing model from the issue text.