Add standardized planner content blocks helper (community module)

### What

Add a small, read-only helper that converts planner-produced `google.genai.types.Part` lists into provider-agnostic, typed "content blocks" modelled after [LangChain v1's standard content blocks](https://docs.langchain.com/oss/python/langchain/messages#standard-content-blocks).

ADK planners (`PlanReActPlanner`, `BuiltInPlanner`) emit reasoning as parts with `thought=True`, and `PlanReActPlanner` additionally annotates text with inline `/*PLANNING*/`-style tags that consumers must parse by hand. This helper turns that into a list of typed blocks — `reasoning` (with a `reasoning_kind` of planning/replanning/reasoning/action), `text`, and `tool_call` — so consumers branch on a `type` discriminator instead of re-parsing raw text.

It is **additive and read-only**: it never mutates the parts and doesn't change how planners build instructions or post-process responses. Existing consumers of the `Part` output are unaffected.

### Background

Originally proposed in core ADK (google/adk-python#6185). That PR was closed and the maintainer suggested the feature belongs in `adk-python-community` as a community module. This issue tracks landing it here.

### Proposed location

New module `src/google/adk_community/planners/` exporting `parts_to_content_blocks` / `part_to_content_block` (plus the `ReasoningContentBlock` / `TextContentBlock` / `ToolCallContentBlock` TypedDicts, `ReasoningKind`, and `ContentBlock`). Self-contained — depends only on `google-genai` (already a transitive dependency via `google-adk`), so no new optional-dependency group is needed. Unit tests under `tests/unittests/planners/`.

A PR implementing this is ready to open.

Comienza con la ruta de módulo propuesta src/google/adk_community/planners/ e inspecciona google.genai.types.Part y los bloques de contenido estándar de LangChain v1. Implementa los helpers de conversión de solo lectura y los tipos TypedDict descritos en el issue; después, añade pruebas unitarias en tests/unittests/planners/. Se considera terminado cuando los bloques reasoning, text y tool_call exponen los discriminadores de tipo y los tipos de reasoning indicados sin mutar las parts de entrada.

Escrito por el modelo de indexación a partir del texto del issue.