dify - 💡(How to fix) Fix [Refactor/Chore] Cap non-dev dependency ranges below next major versions

Description

Several non-development dependency declarations allow automatic upgrades across major versions through open-ended >= constraints. This can let dependency resolution pull in major releases with breaking changes for runtime, optional runtime, provider, storage, and tool dependencies.

Update dependency metadata so non-dev dependencies keep their existing lower bounds but add upper bounds below the next major version. Development-only dependencies should remain exempt.

Motivation

Major dependency upgrades should be deliberate because they can introduce breaking API, packaging, or runtime behavior changes. Adding upper bounds keeps routine dependency resolution safer while still allowing patch and minor upgrades.

Additional Context

Scope includes backend API dependencies, Dify Agent runtime/server dependencies, provider package dependencies, uv override metadata, and generated lockfile metadata.