Disabling UDP/TCP connections does not disable them

### Describe the Bug

I created some UDP and TCP public ressources. They work as expected.
When I set the toggle for the ressources to "disable" in the Pangolin UI, they are still accessible until I restart the pangolin container stack. Reenabling them does work without a restart of the containers.

### Environment

- OS Type & Version: Debian 13
- Pangolin Version: 1.22.2
- Edition (Community or Enterprise): Enterprise , personal use
- Gerbil Version: 1.5.1
- Traefik Version: 3.7
- Newt Version: 1.16.0
- Client Version: -

### To Reproduce

1) Create a public UDP / TCP ressource, configure it/them as desired and check if they are working as expected
2) Set the toggle of the ressources to disable in the UI
3) Check if the ressources are still acceesible

FYI, toggle for http ressources are working as expected -> disables and enables the ressource.

### AI Disclosure

written by myself

### Expected Behavior

The resources should not be accessable anymore after the toggle in the UI is set to disabled for the UDP/TCP ressources

Start by tracing the Pangolin UI resource-toggle request and the reload or configuration path used for UDP and TCP resources, comparing it with the working HTTP path. Reproduce the issue with a public UDP or TCP resource, then verify that disabling it makes the resource inaccessible without restarting the container stack and that re-enabling still works.

Written by the indexing model from the issue text.