kube-proxy fails to sync in nftables mode when newer nftables sets exist

What's the problem?

### What happened? kube-proxy crashes repeatedly, causing the container network to not function. ``` E0205 20:24:21.385767 1 proxier.go:1217] "Failed to list existing sets" err="failed to run nft: signal: segmentation fault (core dumped)" ipFamily="IPv4" E0205 20:24:22.721950 1 proxier.go:1788] "nftables sync failed" err="signal: segmentation fault (core dumped)" ipFamily="IPv4" I0205 20:24:22.723136 1 proxier.go:1143] "Sync failed" ipFamily="IPv4" retryingTime="30s" E0205 20:24:23.698591 1 proxier.go:1217] "Failed to list existing sets" err="failed to run nft: signal: segmentation fault (core dumped)" ipFamily="IPv6" E0205 20:24:24.761438 1 proxier.go:1788] "nftables sync failed" err="signal: segmentation fault (core dumped)" ipFamily="IPv6" I0205 20:24:24.761928 1 proxier.go:1143] "Sync failed" ipFamily="IPv6" retryingTime="30s" ``` ### What did you expect to happen? kube-proxy should correctly setup nftables rules. ### How can we reproduce it...