bpf: remove CRITICAL sections from mainline networking programs

All mainline networking programs are critical by default.

It is still parsed by the platform and uprobestats bpf loaders,
but not by NetBpfLoad, where criticality is simply hardcoded.

You can cs/ for
  ["]critical["] file:bpf
in android and it'll find the relevant:
  ret = readSectionByName("critical", elfFile, critical);
lines.

Test: TreeHugger
Flag: EXEMPT dead code removal
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: I983d0072168a89d81aa9a1e79a1e6f94bf8e822b

bpf/progs/clatd.c

@@ -401,4 +401,3 @@ DEFINE_BPF_PROG("schedcls/egress4/clat_rawip", AID_ROOT, AID_SYSTEM, sched_cls_e
 }
 
 LICENSE("Apache 2.0");
-CRITICAL("Connectivity");

bpf/progs/dscpPolicy.c

@@ -278,4 +278,3 @@ DEFINE_BPF_PROG_KVER("schedcls/set_dscp_ether", AID_ROOT, AID_SYSTEM, schedcls_s
 }
 
 LICENSE("Apache 2.0");
-CRITICAL("Connectivity");

bpf/progs/netd.c

@@ -902,4 +902,3 @@ DEFINE_NETD_V_BPF_PROG_KVER("setsockopt/prog", setsockopt_prog, KVER_5_4)
 }
 
 LICENSE("Apache 2.0");
-CRITICAL("Connectivity and netd");

bpf/progs/offload.c

@@ -820,4 +820,3 @@ DEFINE_XDP_PROG("xdp/tether_upstream_rawip",
 }
 
 LICENSE("Apache 2.0");
-CRITICAL("Connectivity (Tethering)");

bpf/progs/test.c

@@ -43,4 +43,3 @@ DEFINE_BPF_PROG_KVER("skfilter/match", AID_ROOT, AID_ROOT, match, KVER_INF)
 }
 
 LICENSE("Apache 2.0");
-CRITICAL("Networking xTS tests");