The CT dump currently shows swapped src/dst address entries even
though it's correctly using src address resp. dst address as data.

Issue is that 7afe903203c3 ("bpf: Global 5 tuple conntrack.") did
not swap the initial tuple for the lookup when converting from
local to global table, and all the current code right now is doing
workarounds in order to not break CT table during version upgrade.

Thus same needs to be done here for the dump. Issue became more
apparent after aaf6ba39ad4e ("ctmap: Fix order of CtKey{4,6} struct
fields"), which might have had been swapped on purpose but without
further comments in the code on why it was swapped on daemon side.

In this case, reverting aaf6ba39ad4e doesn't fully fix it either
since then direction also needs to be swapped. Instead, make it
less confusing and only swap what needs to be swapped, that is, the
address parts since in the datapath this is the only thing that
should have been done but was missed back then. For next major
version upgrade (aka 2.0), this will be properly fixed (at the
cost of disruptive upgrade).

Fixes: 7afe903203c3 ("bpf: Global 5 tuple conntrack.")
Fixes: aaf6ba39ad4e ("ctmap: Fix order of CtKey{4,6} struct fields")
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>