chore: pin dependencies

[Shreyas-Microsoft]

Purpose

This pull request updates the dependency management for both the ContentProcessor and ContentProcessorAPI projects. The main change is switching all dependencies from version ranges (using >=) to strict, pinned versions (using ==) in both pyproject.toml and requirements.txt files. This ensures consistent and reproducible builds across environments.

Dependency pinning for reproducibility:

• All runtime and development dependencies in src/ContentProcessor/pyproject.toml are now pinned to exact versions instead of allowing any version greater than a minimum. This affects both the main and dev dependency groups.
• The src/ContentProcessor/requirements.txt file has been updated to use only pinned versions for every dependency, matching the changes in pyproject.toml.
• Similarly, all dependencies in src/ContentProcessorAPI/pyproject.toml are now pinned to specific versions, including both runtime and development packages.

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information

[Shreyas-Microsoft]

This is not required any more as we have the uv.lock file changes