chore: regenerate for the graph mutation audit

[jfrench9]

Summary

Regenerated against the RoboSystems API with the graph mutation audit (robosystems #1569). Adds list_graph_mutations, the read of a graph's mutation audit, and picks up additive changes already on the API.

Merge and publish only after robosystems #1569 is merged and its release is deployed. Until then production answers list_graph_mutations with a 404.

Changes

All generated; nothing hand-written changed.

• New: robosystems_client.api.graph_audit.list_graph_mutations (sync and async), wrapping GET /v1/graphs/{graph_id}/audit/mutations. New models: MutationAuditEntry, MutationAuditListResponse, MutationAuditEntryStatus, MutationAuditEntrySurface and ListGraphMutationsSurfaceType0.
• Picked up from the API (already in the deployed v1.14.5):
  • an optional allow_unposted_source_events on ClosePeriodOperation and BackfillPlanHistoryOperation;
  • optional unposted_source_event_count / unposted_source_event_sample on FiscalCalendarResponse, and the matching GraphQL fields in schema.graphql;
  • clearer descriptions on ingest_file, cancel_operation, create_mapping_association, FactSetLite, IngestFileOp and MaterializeOp.

Compatibility

ADDITIVE. One new module and its models. Every changed model gained only optional fields with defaults, checked model by model; nothing became required or was removed. No facade or other stable-tier symbol changed.

Testing

• just test-all: ruff, format, basedpyright, and 595 passed, 17 skipped.
• The regeneration read a local API running the robosystems branch behind #1569 (v1.14.5 plus the audit work, nothing else), so this is exactly the surface that PR ships.