Refactor Python agent SDK to separate core capabilities from ADK and A2A adapters

The current Python agent SDK package (\`a2ui-agent-sdk\`) bundles the core agent-side A2UI capabilities (prompt generation,
streaming parsing, and validation) together with Google ADK (Agent Development Kit) toolsets and A2A (Agent-to-Agent) transport
converters.

This coupling makes the agent SDK heavy and ties it directly to the Google ADK and A2A packages, preventing developers from using
A2UI with other agent frameworks (such as LangChain, LlamaIndex, or custom orchestration loops) without dragging in unnecessary
dependencies.

To improve modularity and future-proofing, we should refactor the codebase to separate the core agent capabilities from the
framework-specific adapters. Furthermore, these adapters should be split into completely separate Python packages so they can be
installed independently.

Examine the current `a2ui-agent-sdk` package structure to identify core capabilities (prompt generation, streaming parsing, validation) versus ADK and A2A adapter code. The goal is to extract adapters into separate packages, likely starting with the main SDK module and dependency definitions. Look for entry points in setup.py or pyproject.toml and existing import statements. 'Done' means the core SDK can be installed without Google ADK or A2A dependencies, and adapters are in their own installable packages.

Written by the indexing model from the issue text.