increase default timeout

[sitaram-kalluri]

- What I did
With maxWaitMilliSeconds = 3000, for the servers with more commit Id's, timeout occurs even before the server could respond resulting in the app's initial sync in-progress run loop.
Attaching the error log snippet

I/flutter (24307): FINER|2022-03-03 18:03:58.810526|SyncService|** syncBuilder sync:from:-1:limit:10:(.wavi|atconnections|[0-9a-f]{8}(?:-[0-9a-f]{4}){3}-[0-9a-f]{12})

I/flutter (24307):  

I/flutter (24307): SEVERE|2022-03-03 18:04:03.002806|AtLookup|Exception in sending to server, Exception: No response after 3000 millis from remote secondary 

I/flutter (24307): SEVERE|2022-03-03 18:04:03.004303|AtLookup|Error in remote verb execution Exception: No response after 3000 millis from remote secondary 

I/flutter (24307): SEVERE|2022-03-03 18:04:03.011904|SyncService|Exception in sync f8ae89cf-31db-4d68-ac5d-2f1c017d6b4c. Reason AT0023: Timeout waiting for response 

I/flutter (24307): SEVERE|2022-03-03 18:04:07.057618|AtLookup|Exception in sending to server, Exception: No response after 3000 millis from remote secondary 

I/flutter (24307): SEVERE|2022-03-03 18:04:07.057974|AtLookup|Error in remote verb execution Exception: No response after 3000 millis from remote secondary 

I/flutter (24307): SEVERE|2022-03-03 18:04:07.058443|SyncUtil|Exception occurred in processing stats verb AT0023 - Timeout waiting for response 

I/flutter (24307): SEVERE|2022-03-03 18:04:10.935073|AtLookup|Exception in sending to server, Exception: No response after 3000 millis from remote secondary 

I/flutter (24307): SEVERE|2022-03-03 18:04:10.935832|AtLookup|Error in remote verb execution Exception: No response after 3000 millis from remote secondary 

I/flutter (24307): SEVERE|2022-03-03 18:04:10.936618|SyncUtil|Exception occurred in processing stats verb AT0023 - Timeout waiting for response 

To overcome the issue, increased the wait time to 10000 milliseconds(10 seconds).

- How I did it
In read method, set maxWaitMilliSeconds to 10000.

- Description for the changelog
Increase the default timeout.

[gkc]

Increasing timeout is OK for a short-term patch, but only masks the actual problem which is why it takes so long to respond. We should discuss this in more detail, but I'm good with this change as an immediate fix.