Use uv instead of pip in development env

[edenhaus]

Breaking change

Proposed change

Replace pip by uv in the development environment including all scripts and dev container
Split from #112496

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[autinerd]

I tested it now on a fresh live system and it works without problems regardless whether uv is already installed or not. For me it looks good to go :) (I can't judge about the Docker part, however)

[edenhaus]

Tested it codespaces/dev container and also locally on arch. Feel free to test it in different dev envs :)

[frenck]

Looks good to me @edenhaus 👍

../Frenck

[farmio]

I do get

home-assistant/script/run-in-env.sh: line 16: VIRTUAL_ENV: unbound variable

now when pre-commit runs mypy and pylint from GitHub Desktop App. Using pre-commit run from terminal works fine 🙃