Revert and fix ip rules

[NikAleksandrov]

This set is a second attempt at reverting the revert PR #24756, which was reverting #24288 and #24577

The upgrade problem mentioned in PR #24756 was due to wrongfully assuming that DeleteRule()
was handling both IPv4 and IPv6. Turns out there was a specific DeleteRuleIPv6() function
which seems unnecessary, so there is 1 additional patch prior to the last revert which changes DeleteRule() and adds
a new family argument, then removes DeleteRuleIPv6(). The problem manifested only when both IPv4 and IPv6 were
enabled due to the IPv6 rule deletion which was actually removing the IPv4 rule.

Note I have removed the "Revert revert" in the patch titles to make checkpatch happy.

The upgrade was tested as:

$ helm install cilium install/cilium/cilium --version 1.13.2 --namespace kube-system --set ipv6.enabled=true

<make sure ip -d rule show has "proto unspec">

$ helm upgrade cilium install/kubernetes/cilium  --set image.override=192.168.122.1:5000/cilium/cilium-dev:latest --set ipv6.enabled=true --namespace kube-system
# upgrade to a local registry with patched cilium image

<make sure ip -d rule show now has "proto kernel" and there is connectivity>

[jrajahalme]

Removing release blocker 1.14 as this is already in v1.14: a63aabc

[julianwiedmann]

I dropped the PR from the 1.13 backport queue for now, let's not set wrong expectations.

[mfoliveira]

Hi @nebril

nebril added this to Needs backport from main in 1.13.17 last week
nebril removed this from Needs backport from main in 1.13.16 last week
nebril removed this from Needs backport from main in 1.13.17 last week

Apparently, this indicates that attempts to queue this for backporting to 1.13.x are over; is that correct?

If at all possible, could you please describe the concerns? (e.g., CI regressions, regression potential, community help with the backport is needed)

Thank you, and have a great weekend!