[avalanche] fix timestamp flakiness in abc_p2p_avalanche_remote_proof…

…s.py

Summary:
The remote proofs returned by the `getremoteproof` RPC contain a "last_update" timestamp. To ensure the comparison between the expected and actual remote proofs does not fail because of a short timing issue, we need to ensure the inbound connection is added after the mocktime is set for the node.

The inbound connections are used for remote proofs since D14961.

Test Plan:
```
alias testr="~/dev/bitcoin-abc/build/test/functional/test_runner.py"
for i in {0..20}; do  testr abc_p2p_avalanche_remote* ; done
```

Reviewers: #bitcoin_abc, Fabien

Reviewed By: #bitcoin_abc, Fabien

Differential Revision: https://reviews.bitcoinabc.org/D14980

test/functional/abc_p2p_avalanche_remote_proofs.py

@@ -49,11 +49,11 @@ def run_test(self):
         self.disconnect_nodes(0, 1)
         node = self.nodes[0]
 
-        inbound = get_ava_p2p_interface(self, node)
-
         now = int(time.time())
         node.setmocktime(now)
 
+        inbound = get_ava_p2p_interface(self, node)
+
         outbound = node.add_outbound_p2p_connection(
             AvaP2PInterface(self, node),
             p2p_idx=1,