There is no reasonable case where a user has pkg_resources-accessible
metadata (or importlib-metadata) and does not have a `_version.py` file.

Instead of replacing with importlib-metadata, I'm just skipping ahead to
the hard-coded "unknown", using `0+unknown` to satisfy PEP440.

There may be a very rare case where someone makes an editable
installation and borks their directory, but knowing what the version was
when they installed it won't help us a lot there.

RF: Add `resamping.apply` to top module imports

Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 3 to 4.
- [Release notes](https://github.com/astral-sh/setup-uv/releases)
- [Commits](astral-sh/setup-uv@v3...v4)

---
updated-dependencies:
- dependency-name: astral-sh/setup-uv
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 4 to 5.
- [Release notes](https://github.com/codecov/codecov-action/releases)
- [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md)
- [Commits](codecov/codecov-action@v4...v5)

---
updated-dependencies:
- dependency-name: codecov/codecov-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

…/setup-uv-4

build(deps): bump astral-sh/setup-uv from 3 to 4

fix: Remove pkg_resources dependency

…odecov-action-5

build(deps): bump codecov/codecov-action from 4 to 5