Flaky End-to-End test on CI

[soareschen]

The CI sometimes fail with the following errors, even when a PR contains only trivial changes:

Traceback (most recent call last):
  File "/relayer/e2e/run.py", line 266, in <module>
    main()
  File "/relayer/e2e/run.py", line 244, in main
    passive_packets(config, ibc0, ibc1, port_id, ibc0_chan_id, ibc1_chan_id)
  File "/relayer/e2e/run.py", line 112, in passive_packets
    assert (len(unreceived) == 0), (unreceived,
AssertionError: ([5, 6, 7, 8], 'unreceived acks mismatch (expected 0)')

A possible fix is to increase the delay in the Python script before querying for unreceived packets.

Acceptance Criteria

Fix the flaky test by submitting a PR fix and re-running the E2E test a few times on the CI. Note that we cannot fully confirm that a fix really works until it is merged, and that subsequent E2E tests are no longer flaky.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate milestone (priority) applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned