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`.

Commencez par examiner SessionContext::add_analyzer_rule, l’issue #1574 et le travail upstream pour un bridge FFI_AnalyzerRule. La tâche sera prête lorsque les bindings Python pourront exposer des règles d’analyse qui transforment de manière significative les plans logiques, y compris le support requis de LogicalPlan.

Rédigé par le modèle d'indexation à partir du texte de l'issue.