chore(runtime): refresh script lock for release 0.8.0

[pmasiphelps]

Prepare for 0.8.0 failed its runtime lock freshness check because resolving the latest allowed transitive dependencies changed the committed script lock. Refresh runtime/run_mcp.py.lock with uv lock --script runtime/run_mcp.py --upgrade; direct dependency pins remain unchanged.

Validation:

• Locked dependency sync, all pre-commit checks, 642 project-environment tests, package build, and Conventional Commit validation passed.
• Exported the refreshed runtime lock and tested its dependencies on Python 3.10 and 3.14: 641 tests passed on each initial run; the remaining release test required the dev environment's Commitizen executable on PATH and passed on targeted reruns.
• The actual locked stdio launcher initialized and listed 129 tools without a live Dataiku connection.
• Lock validation passed, and a second upgrade produced an identical lockfile.

After review and passing CI, squash-merge into release/0.8.0 and dispatch Bump version again from main with operation=prepare and release_branch=release/0.8.0.