chore: Parcel Sync instrumented tests

[sdsantos]

No description provided.

[gnarea]

@sdsantos, following up on #149 (comment), I think parcelDelivery_invalidParcel is now failing because the server isn't available when we make the request:

java.lang.Exception: Unexpected exception, expected<tech.relaycorp.poweb.RejectedParcelException> but was<tech.relaycorp.poweb.ServerConnectionException>
(...)
Caused by tech.relaycorp.poweb.ServerConnectionException: Failed to connect to http://127.0.0.1:13276/v1/parcels
(...)
Caused by: java.net.ConnectException: Failed to connect to /127.0.0.1:13276
(...)
Caused by: java.net.ConnectException: failed to connect to /127.0.0.1 (port 13276) from /127.0.0.1 (port 43068) after 10000ms: (...)
Caused by: android.system.ErrnoException: isConnected failed: ECONNREFUSED (Connection refused)

[gnarea]

Wait what!? My last two commits seem to have fixed the instrumentation test suite. But I'd just tested them in a separate branch where I implemented them as a POC and the test failed with the error above: parcel-delivery-instrumented-test...IOException-bugfix-poc

I suspect this is still an intermittent issue, but maybe my commits made them less frequent: relaycorp/awala-poweb-jvm#63 makes the client retry if it can't connect to the server the first time round.

I'm re-running the CI to see what happens next.

[gnarea]

Yeah, my latest changes have unintentionally made the issue less frequent, but the test is still flaky: https://console.firebase.google.com/u/0/project/relaynet-gateway-android/testlab/histories/bh.fce322cdd2254629/matrices/6458808712135122226 (that's for the last CI run)

I think the test should wait until the server is ready to receive connections.

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

• v1.0.0
• GitHub release

Your semantic-release bot 📦🚀