Improve resync wrt ES WrongExpectedVersionException

[bartelink]

Current behavior is to attempt a re-read without a backoff delay; in prod this is regularly failing despite 3 retries (it's a short stream and the typical timespan is <10ms so the conflict never resolves and the app is yielding excessive 500s as a result).

Considerations:

• Ideally the API will accommodate varying the backoff per transaction (similarly to how the current attempts count is per-transaction not connection-wide)
• If there is a way to request a read from the master node (perhaps after the first retry?), we should do that (a secondary connection might be overkill)

See https://github.com/EventStore/EventStore/issues/1626

[dongdongcai]

I think it can be implemented in Equinox since we can specify the consistency level for read query. By default, the read query is session consistency but when it failed because of wrongversion. We can then set the consistency level for read query to strong consistency by changing the feedoption for qurey.

[bartelink]

See also https://github.com/EventStore/EventStore-Client-Dotnet/issues/312 - resolving by introducing a twin connection policy which has equivalent scalability but does not require backoffs