fix: memberlist-kv startup error (#42)

Prevent Podman 5's Pasta port handler from configuring a network stack
that causes Loki startup errors. The previous rootlesskit port handler
always set up a tap0 interface with a private IP address, which appears
to be required for Loki 3.4 to start correctly. Pasta, instead, assigns
the same IP and name as the main host interface, leading to
unpredictable results.

As Debian 12 with Podman 4 has no Pasta implementation, this fix avoids
using Pasta completely.

Refs NethServer/dev#7426

Author: DavidePrincipi

imageroot/systemd/user/loki.service

@@ -13,6 +13,7 @@ ExecStartPre=/usr/bin/podman pod create \
     --infra-conmon-pidfile %t/loki.pid \
     --pod-id-file %t/loki.pod-id \
     --name loki \
+    --network=slirp4netns:port_handler=rootlesskit \
     --publish ${LOKI_HTTP_PORT}:8080 \
     --replace
 ExecStart=/usr/bin/podman pod start --pod-id-file %t/loki.pod-id