chore: adopt the NAPALM driver standard

- CI moves to .gitea/workflows/ci.yml and calls the shared driver workflow
  of NAPALM/driver-standard; .github/ is gone.
- napalm-device-types >=4.21.1 from PyPI (the floor was 0.4.0).
- LICENSE, CHANGELOG, py.typed, SPDX license string, setuptools>=77,
  version floors on the dev extra (black is gone), links to git.netork.io;
  the README names Python 3.10 and the Gitea CI.
- mypy strict for the package; napalm_fritzbox.fritzbox is exempt for now
  (6 errors), recorded in the quality baseline with four long getters.
- Coverage floor 81 % (measured 81.36 %).

README.md

@@ -6,8 +6,9 @@ NAPALM community driver for **AVM FritzBox** routers (read-only, via TR-064).
 
 | Dependency | Minimum version |
 |---|---|
-| Python | 3.9 |
+| Python | 3.10 |
 | NAPALM | 4.0 |
+| napalm-device-types | 4.21.1 |
 | fritzconnection | 1.13 |
 
 ## Installation
@@ -19,7 +20,7 @@ pip install napalm-fritzbox
 Or from source:
 
 ```bash
-git clone https://github.com/napalm-automation-community/napalm-fritzbox
+git clone https://git.netork.io/NAPALM/napalm-fritzbox
 cd napalm-fritzbox
 pip install -e .
 ```
@@ -78,18 +79,16 @@ does not verify it, so no separate `verify` option is needed.
 
 ## Development
 
+The rules are in [STANDARDS.md](https://git.netork.io/NAPALM/driver-standard/src/branch/main/STANDARDS.md).
+
 ```bash
-pip install -e ".[dev]"
-pytest tests/
+python -m venv .venv && .venv/bin/pip install -e ".[dev]"
+.venv/bin/pytest --cov
 ```
 
-## CI
-
-This project includes a GitHub Actions workflow that:
-- Runs unit tests across Python 3.9–3.12
-- Builds sdist and wheel
-
-See [.github/workflows/ci.yml](.github/workflows/ci.yml).
+CI ([.gitea/workflows/ci.yml](.gitea/workflows/ci.yml)) calls the shared workflow of
+the NAPALM driver standard: ruff, mypy, the tests on Python 3.10–3.13, bandit,
+pip-audit and a build check.
 
 ## License