fix(relay): upgrade to 0.7.1

[bbednarski9]

What does this PR do?

Upgrades Hermes's NeMo Relay requirement from >=0.6.0,<0.7 to >=0.7.1,<0.8 and refreshes uv.lock to the published 0.7.1 wheels.

This is intentionally limited to the dependency upgrade. It does not include the plugin-initialization or dynamic-plugin work from #77915.

Relay 0.6 can starve its shared Tokio worker pool after timed-out concurrent tool callbacks remain blocked. A later Relay-managed sequential tool call then cannot enter its Python callback, leaving the Hermes turn permanently stuck. Relay 0.7 dispatches Python callbacks on their originating Python event loop instead, so a later managed call can proceed even while earlier callbacks remain blocked.

This resolves the confirmed cross-call starvation mechanism in #79568. It does not identify or make cancellable the original operation that caused the first tools to block; that remains separate root-cause work.

Related Issue

Fixes #79568

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

• pyproject.toml: require nemo-relay>=0.7.1,<0.8 on Hermes's supported Relay wheel targets.
• uv.lock: resolve the published nemo-relay 0.7.1 distribution and platform wheels.

How to Test

1. Run uv lock --check.
2. Confirm uv.lock resolves nemo-relay to 0.7.1.
3. Reproduce [Bug]: Sequential tool execution has no deadline — a wedged tool silently hangs the turn forever #79568's saturated-callback scenario: a later sequential Relay-managed tool call should enter and complete instead of waiting for blocked Relay 0.6 callback workers.

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (not needed for a dependency-only upgrade)
• I've tested on my platform: macOS arm64 (uv lock --check)

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — N/A; dependency-only upgrade
• I've updated cli-config.yaml.example if I added/changed config keys — N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide
• I've updated tool descriptions/schemas if I changed tool behavior — N/A

For New Skills

Not applicable.

Screenshots / Logs

uv lock --check
Resolved 250 packages
nemo-relay 0.7.1