chore(deps): regenerate lockfiles and requirements to pin moss 1.1.1

[riit3sh]

Pull Request Checklist

Please ensure that your PR meets the following requirements:

• I have read the CONTRIBUTING guide.
• I have updated the documentation (if applicable).
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.

Description

This PR regenerates and updates 18 uv.lock files, 31 pyproject.toml manifests, and source requirements.txt files across all packages, cookbooks, voice agents, and applications in the repository to pin and require moss>=1.1.1 (and inferedge-moss-core to 0.12.1).

Context & Motivation:

• The recent 1.1.1 release resolves critical model download connection timeouts (Query error: failed to load embedding model 'moss-minilm': model download failed...) and remote 503 query fallback bugs.
• However, all pre-existing lockfiles and package declarations in the repository were still pinned to either 1.1.0 or older 1.0.x/1.0.1 targets. Anyone checking out the repository and executing these integrations/voice-agents would pull the older, buggy dependencies and hit the timeouts.
• Updating all 49 lockfiles, pyproject.toml manifests, and requirements files ensures that every single Python app, data connector, voice agent, and cookbook integration uses the stable 1.1.1 version of the SDK out of the box (regardless of whether they install via standard pip or uv locking), allowing on-device querying to run flawlessly in under 2ms.

Verification & Local Tests:

• Ran the updated load_and_query_sample.py in the standard examples/python directory using the new moss>=1.1.1 package. The index prewarmed cleanly and queries returned successfully in 2ms (with 0ms for sub-millisecond local hotpath queries!).
• Set up the local development environment for the Python SDK and ran the test suite:
  • Result: 86 passed, 44 skipped (with E2E integration tests safely auto-skipping due to omitted cloud credentials as expected). No regressions.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.