feat(csa): expose canonical configuration manifests

[isty2e]

Summary

CSAOptimizer.from_space_defaults(...) resolves presets, space-derived components, and explicit overrides into the configuration that actually runs. This PR makes that resolved optimizer-side configuration available as stable, JSON-safe provenance.

• add an immutable, versioned CSAConfigurationManifest with strict to_dict() / from_dict(), canonical JSON, and a SHA-256 content fingerprint
• project exact built-in spaces, samplers, diversity metrics, operators, and every resolved CSA profile field through contract-owned encoders
• require explicit CSAComponentDescriptor values for custom component occurrences and report all missing and unused semantic paths together
• expose the three provenance artifacts through the supported population and advanced CSA facades
• document persistence, custom descriptors, semantic paths, version axes, fingerprint limits, and checkpoint-restore guards

Contract boundaries

The manifest describes resolved optimizer configuration only. It does not serialize executable Python objects, runtime RNG state, checkpoints, problems, objectives, datasets, evaluators, dependency versions, or the execution environment.

Custom descriptors are caller assertions. Variopt validates and fingerprints their identifiers, versions, and JSON configuration, but matching descriptors are not proof that two custom implementations behave identically. The fingerprint is therefore a version-scoped identity for represented manifest data, not a complete run or reproducibility identity.

Manifest generation is read-only and remains outside optimization hot paths. random_state=None is represented as nondeterministic initialization without materializing an RNG snapshot.

Validation

• uv run ruff check --fix --extend-select I,UP pyproject.toml src tests .github/scripts
• uv run ruff format --check pyproject.toml src tests .github/scripts
• uv run basedpyright src tests .github/scripts (0 errors, 0 warnings)
• uv run pytest tests -q (1692 passed)
• uv run --extra docs mkdocs build --strict
• uv build --wheel
• isolated installed-wheel base-surface smoke test
• built-in and custom-component documentation examples executed directly

Closes #95