Expose SessionContext.add_analyzer_rule for Python-defined analyzer rules

## Background

`SessionContext::add_analyzer_rule` registers an `Arc` that runs during plan analysis (the pre-optimization pass that resolves names, applies type coercion, etc.). The Python bindings do not expose this method.

## Upstream signature

```rust
pub fn add_analyzer_rule(&self, analyzer_rule: Arc)
```

## User value

Lets users intercept and transform a logical plan immediately after analysis, before the main optimizer runs. Useful for custom semantic validation, injecting domain-specific defaults, or rewriting unresolved references against an external catalog.

## Why deferred

Blocked upstream, same root cause as #1574 ([add_optimizer_rule](https://github.com/apache/datafusion-python/issues/1574)): no FFI bridge exists for the logical `AnalyzerRule` trait, and a Python-only adapter can observe but not meaningfully transform `LogicalPlan` nodes because there are no Python constructors for the variants. Tracked here; revisit when upstream lands an `FFI_AnalyzerRule`.

首先檢視 SessionContext::add_analyzer_rule、issue #1574，以及用於實作 FFI_AnalyzerRule bridge 的上游工作。當 Python bindings 能夠公開可對邏輯計畫進行有意義轉換的分析規則，並包含所需的 LogicalPlan 支援時，此任務即可完成。

由索引模型根據 Issue 內容生成。