handle the case of avaproof message before avahello: discourage the peer and ignore the proof

address the easy items of the review*, and also remove node from queue when it sends a duplicate proof (we ban it anyway)

don't register the nodes while IBD is ongoing. Queue them for later.

@bot build-linux-arm build-linux-aarch64

Node registration must be postponed after end of IBD.

rebase

rebase

This needs rebase

Less ambiguous send/receive icons

There are still quite a few unit tests to be changed. We can no longer just take a random uint32 to create a valid proof, it must be in the correct range.

Wordings looks fine to me.

Better active pane underline css (previously did not line up in Firefox)

Based on D9342, we can potentially register the proof earlier depending on the proofs ValidationState at init.

rebase on master after landing D9342

drop the if

I suspect that the if (!g_avalanche) test will never be true. In init.cpp, g_avalanche is set in step 7 before the node actually starts connecting to peers (step 12).

move & add comments