Migrate from conda to uv

[rosmur]

Summary

This PR migrates the project from conda to uv for dependency management. uv is the modern, performant option and has become the de facto standard in the ecosystem now.

Changes

• Added requires-python = ">=3.9" to pyproject.toml for proper Python version specification
• Generated uv.lock for reproducible dependency resolution
• Removed requirements.txt and requirements.in to enable pyproject.toml as the single source of truth
• Updated README with clear uv installation and usage instructions. Includes fallback instructions for pip users who can generate requirements.txt if needed

Testing

• Verified uv sync successfully installs all dependencies
• Tested uv run sharp --help works correctly
• Confirmed all project dependencies are properly declared in pyproject.toml

[rosmur]

Migration Notes

Users can now use:

uv sync
uv run sharp --help

[truedat101]

Oh, I just made my own fork with some uv "helper" instructions under a new section called quickstart, no code changes : https://github.com/IoTone/ml-sharp/blob/main/README.md#quickstart , my rationale for this is similar to what is suggested in the description. I am noticing a trend that a lot of people who want to try out the tools on their own don't have the background on virtualenvs or managing python toolchain (mis) installation to get anything working. I personally don't see a reason to move people off of pip/conda. Is there any reason why uv instructions couldn't live along side conda/pip? A good CI workflow can ensure all the acceptable ways to build the tools will just work.