fix: separate code sample registry + publish on SDK release

[Nelson-PROIA]

What

Two fixes for the code sample pipeline that Gregory identified in platform-docs #923:

1. Separate registry location

Both client-python and client-ts were publishing code samples to the same Speakeasy registry location (mistral-openapi-code-samples). Last-writer-wins meant only TypeScript samples were available. Changed to:

• Python: mistral-openapi-python-code-samples
• TypeScript: mistral-openapi-typescript-code-samples

2. Publish code samples on SDK release

The publish workflow (sdk_publish_mistralai_sdk.yaml) published to PyPI via uv directly, bypassing Speakeasy. The code sample overlay never got published. Added a step after PyPI publish that runs speakeasy ci generate --push-code-samples-only --target mistralai-sdk to push the Python code samples to the registry.

Files changed

• .speakeasy/workflow.yaml: registry location → mistral-openapi-python-code-samples
• .github/workflows/sdk_publish_mistralai_sdk.yaml: added code sample publish step

Context

• Platform-docs PR #923 (Gregory's fix) identified these issues
• The Python overlay was stale (last updated ~Feb 2026, 75 operations vs 253 for TS)
• After this PR, both Python and TS overlays publish to separate registry locations and stay in sync with every SDK release

[Nelson-PROIA]

Wrong repo. The workflow.yaml source of truth is in the dashboard repo (mistralai/dashboard/client-python/.speakeasy/workflow.yaml). Moving there.