The Hub's network-policy routes create and remove Kubernetes NetworkPolicy
objects and compute pod-reachability impact. That acts outside Kubeshark's own
data, so it is not something a role should carry implicitly and not something
a deployment should offer unasked. It gets the same shape as scripting: a
switch the operator sets, rendering NETWORK_POLICIES_DISABLED for the Hub.
Off by default. The dashboard never calls these routes, so nothing in the UI
changes; a caller that wants them is asking on purpose.