feat: Add enum constraint to agent_name for transfer_to_agent

[qieqieplus]

Current implementation of transfer_to_agent doesn't enforce strict constraints on agent names,
We could use JSON Schema's enum definition to implement stricter constraints:

Before

[{
	"type": "function",
	"function": {
		"name": "transfer_to_agent",
		"description": "Transfer the question to another agent.\n\nThis tool hands off control to another agent when it's more suitable to answer the user's question according to the agent's description.\n\nArgs:\n  agent_name: the agent name to transfer to.\n",
		"parameters": {
			"type": "object",
			"properties": {
				"agent_name": {
					"type": "string"
				}
			}
		}
	}
}]

After

[{
	"type": "function",
	"function": {
		"name": "transfer_to_agent",
		"description": "Transfer the question to another agent.\n\nThis tool hands off control to another agent when it's more suitable to answer the user's question according to the agent's description.\n\nArgs:\n  agent_name: the agent name to transfer to.\n",
		"parameters": {
			"type": "object",
			"properties": {
				"agent_name": {
					"type": "string",
					"enum": ["agent_a", "agent_b", "agent_c"]
				}
			}
		}
	}
}]

[adk-bot]

Response from ADK Triaging Agent

Hello @qieqieplus, thank you for your contribution!

To help us review this PR, could you please:

1. Associate a GitHub issue with this PR. If one doesn't exist, please create one.
2. Add a "Testing Plan" section to the PR description explaining how you've tested these changes.

This information will help reviewers to review your PR more efficiently. Thanks!