Use uv instead of pip on production images

[edenhaus]

Breaking change

Proposed change

Update uv from 0.1.17 to 0.1.22 to have prebuilt binaries for armhf and armv7:

• https://github.com/astral-sh/uv/releases/tag/0.1.18
• https://github.com/astral-sh/uv/releases/tag/0.1.19
• https://github.com/astral-sh/uv/releases/tag/0.1.20
• https://github.com/astral-sh/uv/releases/tag/0.1.21
• https://github.com/astral-sh/uv/releases/tag/0.1.22

The uv version used for production images will be extract from requirements_test.txt to use the same version as in the CI

Comparison of the build base image step:

Arch	Pip 2023.3.1	Pip Nightly (18.03.24)	UV (This PR)
aarch64	1h 38m 46s	1h 24m 53s	5m 18s
armhf	1h 30m 2s	1h 52m 20s	6m 2s
armv7	1h 27m 41s	1h 26m 43s	5m 28s
amd64	18m 49s	22m 10s	3m 20s
i386	23m 5s	17m 37s	3m 11s

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.

[bdraco]

The failing test is a bit slow on gh actions. I fixed it in #112520

[charliermarsh]

Feel free to ping me directly if you run into problems or there's anything we can do to help.

[edenhaus]

@charliermarsh Currently UV is not providing binaries for the following architectures, which we build HA for:

• armhf (CI job)

  [ 2/12] RUN curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.1.17/uv-installer.sh | sh:
  #0 1.466 ERROR: there isn't a package for arm-unknown-linux-musl-dynamiceabihf

• armv7 (CI job)

  [ 2/12] RUN curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.1.17/uv-installer.sh | sh:
  #0 1.352 ERROR: there isn't a package for armv7-unknown-linux-musl-dynamiceabihf

Would it be possible to build binaries for these two arch directly in uv?

[home-assistant]

There is a merge conflict.

[bdraco]

From https://github.com/home-assistant/core/actions/runs/8334291458/job/22807646088:

329.2 Caused by: Failed to download distribution due to network timeout. Try increasing UV_HTTP_TIMEOUT (current value: 300s).

Looks like when the CDN is having issues it needs a lower timeout, and some retries

pip retries on status_forcelist=[500, 502, 503, 520, 527]

[edenhaus]

Test build image pipeline: https://github.com/home-assistant/core/actions/runs/8391747954

Stale

[edenhaus]

FAILED tests/components/axis/test_diagnostics.py::test_entry_diagnostics[api_discovery_items0] - AssertionError

unrelated

[frenck]

Amazing progress! 🎉

Let's see how this is going to behave on our nightly builds 👍

../Frenck