[zewenli98]

Description

This PR adds structured, machine-readable reporting and verification capabilities for Dynamo workflows:

• Introduces analyze() for preflight converter support, partitioning, coverage, and configuration checks without building engines. (dryrun=True is the existing human-oriented debugging mode that skips TensorRT engine conversion and prints or saves a textual partitioning summary, while analyze() is a programmatic preflight API that returns a typed, JSON-serializable AnalysisReport with node eligibility, assignments, fallback reasons, partitions, coverage, checks, diagnostics, and status. analyze() also predicts behavior using the requested compilation settings, isolates graph and weight changes, preserves RNG state, supports structured events, and reports failures without building engines.)
• Introduces compile_with_report() to return the compiled module together with detailed analysis, engine, diagnostic, and timing evidence.
• Introduces validate() to deterministically compare reference and compiled outputs using explicit structure, dtype, shape, tolerance, and nonfinite-value rules while preserving model, input, aliasing, and RNG state.
• Introduces benchmark() to produce reproducible wall-clock and CUDA-event latency, percentile, throughput, and speedup measurements under explicit synchronization and timing semantics.
• Defines versioned JSON contracts and schemas for analysis, compilation, validation, benchmarking, events, environments, and artifact manifests.
• Emits typed, job-scoped events across analysis, partitioning, conversion, and TensorRT engine builds.
• Preserves caller graphs, model/input state, RNG state, and existing compiler behavior.
• Adds CPU/GPU tests, golden schema fixtures, documentation, and CI compatibility checks.

Existing compile() and dryrun APIs remain available with unchanged return types and behavior.

This provides the dependency-free Core API layer for the upcoming MCP PR, which will expose these capabilities as policy-controlled MCP tools and add artifact persistence, job orchestration, and lineage tracking outside the core package.

Fixes #4843

Type of change

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project (You can use the linters)
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas and hacks
• I have made corresponding changes to the documentation
• I have added tests to verify my fix or my feature
• New and existing unit tests pass locally with my changes
• I have added the relevant labels to my PR in so that relevant reviewers are notified