This is a spin-off of https://github.com/realm/realm-core/pull/7291

After Kotlin upgraded to Core 13.25.0, we are seeing a bunch of issues with tests timing out and otherwise behaving weirdly.
One error was related to #7291 (linked above), but after using that branch we are still seeing other issues.

We can reliably reproduce tests hanging by starting a completely fresh BAAS and then running either of these two tests on the JVM:

https://github.com/realm/realm-kotlin/blob/ec7189244d7d1c4f7c5544fdfc0a00a4cf9ceef4/packages/test-sync/src/commonTest/kotlin/io/realm/kotlin/test/mongodb/common/AsymmetricSyncTests.kt#L133 and https://github.com/realm/realm-kotlin/blob/ec7189244d7d1c4f7c5544fdfc0a00a4cf9ceef4/packages/test-sync/src/commonTest/kotlin/io/realm/kotlin/test/mongodb/common/AsymmetricSyncTests.kt#L307

Both of these tests use SyncSession.uploadAllLocalChanges() which ends up timing out after two minutes.

This only happens with Platform Networking enabled. Without it, the tests pass locally. CI however, still experiences timeouts, which (to me) indicates some kind of race condition: https://ci.realm.io/blue/organizations/jenkins/realm%2Frealm-kotlin/detail/PR-1633/42/tests

I attached the logs from a failed attempt locally:
insert_test_baas_server.log.zip
insert_test_timeout.txt

Note, that all our tests detect if the appropriate Test App is present on the server, and if not, use the Admin API to create it. We have then added a wait that monitors that progress/sync report all schemas as complete. However, the Admin API does not create all the schemas up front, so our tests depend on Dev Mode doing the correct thing and creating some of those schemas.

Right now my best guess is that Dev Mode and Sync Bootstrap are somehow causing issues with the Sync Client, but that is just a guess.