Added default parameter ForceWaitTimeout to OpQuery and WaitForReply

[dbcto]

Call of GetInstanceInfo() results in an endless loop in WaitForReply when replicasets may have changed primary and secondary, because there is never any data received even if replicaset got valid again.

[ErikUniformAgri]

I had a similar problem after my internet and the connection were gone for a while. When the connection was reestablished I ended up in the same endless loop in WaitForReply. I used this code and added the ForceWaitTimeOut parameter to TgoMongoCollection.Find and the problem was gone

function TgoMongoCollection.Find(const AFilter,
AProjection: TBytes; const ANumberToSkip : Integer = 0): IgoMongoCursor;
// https://docs.mongodb.com/manual/reference/method/db.collection.find
var
Reply: IgoMongoReply;
begin
Reply := FProtocol.OpQuery(FFullName, [], ANumberToSkip, 0, AFilter, AProjection, True);
HandleTimeout(Reply);
Result := TgoMongoCursor.Create(FProtocol, FFullName, Reply.Documents, Reply.CursorId);
end;

[RadiRadiesel2]

Fork "tuurke63" using StopWatch instead of TDateTime does solve this problem!