[e2e] aztec-node doesn't sync fast enough on 2 core runners

[ludamad]

This seems to come up on the lower core runners. While annoying to uncover it, its a chance to make things more robust :)

Example https://github.com/AztecProtocol/aztec-packages/actions/runs/8540912819/job/23399819123

[benesjan]

I spent some time on this today and the error gets thrown by a callPrivateFunction oracle callback and it gets thrown because it does not find the contract instance in PXE database. The oracle is most likely called from account contract entrypoint (in AppPayload). The name of the problematic contract was not logged so I created this PR which logs all the contract deployments.

The only way for the contract to get to the PXE db is via PXE.registerContract(...) call. Once I have the problematic contract name I'll be able to determine where exactly the contract fails to get added (by comparing it to the logs of passing test).

This not a node sync issue but probably some kind of race condition.

[benesjan]

@ludamad have you stumbled upon this again? If not I would close this.

[ludamad]

I've lost track of what's gone in though I was seeing it a bit ago. We can close it