fix: WireGuard peers keep their tunnel key when others come and go (#32)

get_vpn_tunnels() keyed WireGuard peers with a running counter over the
peer rows, so a peer added ahead of an existing one renumbered every peer
after it. Whatever a consumer stores per key moved with it: netOrk's site
link and tunnel check ended up on a new, offline peer and alarmed while the
real tunnel was up.

The key is now the interface and the start of the public key, as in
napalm-linux, made URL-safe because the key is a path segment. Two peers
sharing the prefix get the whole key; a row without a public key keeps its
position. IPsec and OpenVPN keys were already stable.

Every WireGuard key changes once; netOrk carries its
per-tunnel metadata across (netork#1654).

CHANGELOG.md

@@ -6,6 +6,12 @@ All notable changes to this driver. The format follows
 
 ## [Unreleased]
 
+### Fixed
+- `get_vpn_tunnels()` keys a WireGuard peer by its interface and the start of its
+  public key (`wireguard-wg0-aBcD1234`, URL-safe) instead of its position, so a peer
+  added ahead of another no longer renumbers it (#32). Every WireGuard key changes
+  once with this release.
+
 ## [0.5.0] - 2026-10-23
 
 The first release on PyPI.