Support for the uv package manager (uv.lock)

Hi,

I couldn't find any existing or past issues mentioning this.

It'd be great to support uv for dependency management. It's one of the most widely used Python package managers, and a lot of projects now standardise on uv.lock the way they used to on Pipfile.lock. A good number of our projects at SAP have moved over to uv + uv.lock entirely, and today those apps can't be pushed as-is -- you end up keeping a separate requirements.txt in the repo by hand, purely for compatibility with the CF Python buildpack, which rather defeats the point of having a lockfile.

The nice part is the buildpack already has the right shape for this. pipenv support works by generating a requirements.txt (from Pipfile.lock) and then handing off to the normal pip install path -- uv fits that exact pattern, and uv export exists for precisely this purpose.

Rough idea I'm thinking of would be:

• Detect uv.lock (+ pyproject.toml), much like Pipfile is detected today
• Run uv export --format requirements-txt to turn the lock into a requirements.txt
• Install it with uv pip install (uv's installer is dramatically faster than pip), falling back to pip
• Read the Python version from .python-version / requires-python in pyproject.toml

Routing through a generated requirements.txt keeps all the existing machinery working unchanged, so it should be a reasonably contained change. plus uv ships as a PyPI wheel, so it can be added as a manifest dependency the same way pipenv is.

I'd be happy to put together a PR if this seems worth including.

Thanks!

Inizia tracciando il supporto esistente per Pipfile/Pipfile.lock e il relativo flusso di generazione di requirements.txt, quindi confronta questo percorso con uv export e con il normale flusso di pip install. Il lavoro è completato quando i progetti che contengono uv.lock e pyproject.toml possono essere inviati senza un requirements.txt mantenuto manualmente, con i fallback indicati per la versione di Python e l'installer coperti.