- [ ] Have you followed the guidelines for contributing? - [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? - [ ] Have you successfully run `make lint && make test`? --- Adds `dev-stonking` and `dev-tenacious` dependency groups for the next two Ubuntu development releases, and registers both in the `[tool.uv] conflicts` matrix alongside the existing codename groups. Both pin `python-apt` to the same `~=3.0.0` range as `dev-questing` and `dev-resolute` for now. The `dev-tenacious` pin can be tightened later once that release ships a distinct `python-apt` version. ## Lockfile repair Re-locking also moves `craft-platforms` from 0.10.0 to 0.12.0. This is not an opportunistic upgrade. `uv.lock` on `main` pinned `craft-application` 7.3.0 alongside `craft-platforms` 0.10.0, and that combination is not satisfiable, because `craft-application` 7.3.0 requires `craft-platforms>=0.12.0`. Pinning it back fails resolution: ``` Because craft-application>=7.3.0 depends on craft-platforms>=0.12.0 and craft-platforms==0.10.0, we can conclude that craft-application>=7.3.0 cannot be used. ``` `uv lock --check` does not catch this, because `craft-platforms` is a transitive dependency and is therefore not named in `pyproject.toml`. ## Verification - `make lint-uv-lockfile` and `uv lock --check` pass. - `uv sync --group dev-stonking` and `uv sync --group dev-tenacious` each install `python-apt==3.0.0+ubuntu1`, and `import apt_pkg` then succeeds. - `make test-fast`: 245 passed, 1 skipped, 1 deselected, run against `craft-platforms` 0.12.0. - `make format`: clean. The `make lint && make test` checklist item is left unticked on purpose. `make test` was not run, because it includes the expensive spread suite; `make test-fast` was run instead. `make lint` fails on this branch, but it fails identically on `main`: `lint-ty` emits the same 4 pre-existing diagnostics. That was confirmed by stashing these changes, re-syncing to `craft-platforms` 0.10.0, and re-running the target.