chore: prepare v0.1.1 release

[kaiitunnz]

Purpose

Prepare the repository for the v0.1.1 release by synchronizing all published package versions and first-party pins, while also consolidating the SDK and server runtime version surfaces so future synchronized bumps update one source of truth per runtime.

Changes

• pyproject.toml, cli/pyproject.toml, cli/stack/pyproject.toml, hook/pyproject.toml, sdk/pyproject.toml, sdk/stack/pyproject.toml, uv.lock — bump published package versions and internal first-party == pins from 0.1.0 to 0.1.1.
• scripts/dev/bump_version.py, scripts/ci/check_release_version.py, tests/scripts/test_bump_version.py, tests/scripts/test_check_release_version.py — teach the release helper and validator to manage and verify the dedicated runtime version files, including duplicate-line regression coverage.
• sdk/src/flowmesh/_version.py, sdk/src/flowmesh/__init__.py, sdk/src/flowmesh/_constants.py — move the SDK runtime version and User-Agent onto a dedicated version module and re-export from the public package surface.
• src/shared/_version.py, src/server/main.py — move the server OpenAPI version onto a dedicated shared runtime version file, then rename the internal constant to FLOWMESH_RELEASE_VERSION to avoid colliding with the stack image-tag env var FLOWMESH_VERSION.
• docs/RELEASE.md — minimally update the release-prep wording so it matches the helper's current scope.

Design

The release-prep helper now updates the package metadata plus two dedicated runtime version files: one for the published SDK package and one for the shared server/worker runtime tree. That removes the earlier duplication between package metadata, flowmesh.__version__, and the SDK User-Agent constant.

The server-side constant rename is intentionally narrow. The stack and worker image-tag env var remains FLOWMESH_VERSION; only the internal shared release constant became FLOWMESH_RELEASE_VERSION, which removes the naming collision without taking on a broader env migration in this PR.

Test Plan

uv run pytest tests/scripts/test_bump_version.py tests/scripts/test_check_release_version.py tests/scripts/test_check_image_release.py
uv run scripts/dev/bump_version.py 0.1.1
uv lock
uv run scripts/ci/check_release_version.py --tag v0.1.1
uv run pre-commit run --all-files
uv build --all-packages --out-dir dist
uv run scripts/ci/check_package_build.py --dist dist
uv run pytest tests/ --ignore=tests/worker/test_mp_executor_cleanup_gpu.py

Test Result

• uv run pytest tests/scripts/test_bump_version.py tests/scripts/test_check_release_version.py — passed (6 passed).
• uv run scripts/ci/check_release_version.py --tag v0.1.1 — passed (Release package versions are synchronized at 0.1.1.).
• uv run pre-commit run --files src/shared/_version.py src/server/main.py scripts/dev/bump_version.py scripts/ci/check_release_version.py tests/scripts/test_bump_version.py tests/scripts/test_check_release_version.py — passed.
• uv run pytest tests/scripts/test_bump_version.py — passed (6 passed) after the final doc/test follow-up.
• uv run pre-commit run --files docs/RELEASE.md tests/scripts/test_bump_version.py — passed.
• Earlier on this branch: uv run pre-commit run --all-files passed.
• Earlier on this branch: uv build --all-packages --out-dir dist built all six source distributions and wheels for 0.1.1.
• Earlier on this branch: uv run scripts/ci/check_package_build.py --dist dist passed, including flowmesh --help smoke checks from built artifacts.
• Earlier on this branch: uv run pytest tests/ --ignore=tests/worker/test_mp_executor_cleanup_gpu.py passed (866 passed, 18 warnings).

---

Pre-submission Checklist

• I have read the contribution guidelines.
• I have run pre-commit run --all-files and fixed any issues.
• I have added or updated tests covering my changes (if applicable).
• I have verified that uv run pytest tests/ passes locally.
• If I changed shared schemas or proto definitions, I have checked downstream compatibility across Server and Worker.
• If I changed the SDK or CLI, I have verified the affected packages work (uv sync --all-packages --group ci --frozen).
• If this is a breaking change, I have prefixed the PR title with [BREAKING] and described migration steps above.
• I have updated documentation or config examples if user-facing behavior changed.

[timzsu]

LGTM. Maybe you can update the pr desc to reflect the latest fix?

[timzsu]

LGTM.