workaround for overriding default timeout limitation

[jgao54]

collection.Find hard-codes OmitMaxTimeMs(true) and honors the server-side defaultMaxTimeMS. It's not always practical to ask user to set a very long default timeout on the server-side; however connection string does not support passing maxTimeMS as a parameter. Workaround is to use the generic RunCommandCursor instead of Collection.Find which will derive the maxTimeMS using the context deadline, which us set to 5 days by default on our end

[codecov]

❌ 2 Tests Failed:

Tests completed	Failed	Passed	Skipped
1664	2	1662	166

View the top 2 failed test(s) by shortest run time

github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuitePG_CH_Cluster

Stack Traces | 0.01s run time

=== RUN   TestPeerFlowE2ETestSuitePG_CH_Cluster
=== PAUSE TestPeerFlowE2ETestSuitePG_CH_Cluster
=== CONT  TestPeerFlowE2ETestSuitePG_CH_Cluster
--- FAIL: TestPeerFlowE2ETestSuitePG_CH_Cluster (0.01s)

github.com/PeerDB-io/peerdb/flow/e2e::TestPeerFlowE2ETestSuitePG_CH_Cluster/Test_Unbounded_Numeric_With_FF

Stack Traces | 5.09s run time

=== RUN   TestPeerFlowE2ETestSuitePG_CH_Cluster/Test_Unbounded_Numeric_With_FF
=== PAUSE TestPeerFlowE2ETestSuitePG_CH_Cluster/Test_Unbounded_Numeric_With_FF
=== CONT  TestPeerFlowE2ETestSuitePG_CH_Cluster/Test_Unbounded_Numeric_With_FF
2026/02/17 18:26:03 INFO Received AWS credentials from peer for connector: ci x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
2026/02/17 18:26:03 INFO Received AWS credentials from peer for connector: clickhouse x-peerdb-additional-metadata={Operation:FLOW_OPERATION_UNKNOWN}
    clickhouse_test.go:751: Failed to connect temporal client: failed reaching server: context deadline exceeded
    clickhouse.go:114: begin tearing down postgres schema pgchcl_6gctjo1x
--- FAIL: TestPeerFlowE2ETestSuitePG_CH_Cluster/Test_Unbounded_Numeric_With_FF (5.09s)

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}