[BUG] `agentcore configure --protocol MCP` should automatically disable memory configuration

## Description
When running `agentcore configure --protocol MCP`, the CLI automatically attempts to configure memory. This behavior is incorrect because memory configuration only makes sense in the context of an agent (using `--protocol HTTP`), not for MCP servers.

## Current Behavior
```bash
agentcore configure --protocol MCP
```
Prompts for memory configuration during setup.

## Expected Behavior
When `--protocol MCP` is specified, memory should be automatically disabled without prompting the user, since MCP servers don't use memory in the same way agents do.

## Suggested Fix
The `agentcore configure` command should detect when `--protocol MCP` is used and skip memory configuration entirely, or automatically set memory to disabled.

## Context
MCP (Model Context Protocol) servers are stateless tools that don't require memory persistence, unlike agents that maintain conversational state.

Start at the agentcore configure command's handling of the --protocol option and trace where memory configuration prompts are triggered. Run `agentcore configure --protocol MCP` to reproduce the prompt; done means MCP setup skips memory configuration or disables it automatically without prompting.

Written by the indexing model from the issue text.