Remove pf1 proxy

[PlagueCZ]

As the solution for non-working PF1 in multiport-eswitch has been found, the workaround is no longer needed.

All code is removed and documentation is updated with the mention of missing kernel option in Debian.

Pytest suite is working for on-hardware tests using two locally connected machines and when --port-redundancy option is used this automatically tests if PF1 is working properly otherwise scapy would not be able to see packets returned by the reflector on the other machine.

Fixes #635
Fixes #597

[byteocean]

Thanks a lot for working on removing relevant code for the proxy port. These changes LGTM.

It is a pity that we had to work on such complex workaround, but it is nice that we now get natively supported link redundancy. In this journey, I think we got two key experience, thus I would like to highlight here for future usage:

1. the usage of async templates. the approaches of creating, instantiating match/action templates can be found in Introduce multiport-eswitch mode to support continuous communication #589
2. VF can be used by the hosts to send/receive packets, not just be used by VMs. the relevant code can be found Use mlx5 vf as PF1 proxy #614

[byteocean]

compilation and tests worked well in my environment.

[guvenc]

Thanks. LGTM