Handle SQL Server checkpoint number uncertainty

[dennisdoomen]

See https://dba.stackexchange.com/questions/133556/can-i-rely-on-reading-sql-server-identity-values-in-order/135116#135116.

With SQL Server, there's a slight possibility that checkpoint have gaps because of a ongoing transaction

[dennisdoomen]

See also https://github.com/SQLStreamStore/SQLStreamStore/pull/39/files#diff-27f7cad6583c7686c2009315cd833e0aR58

[IharBury]

I don't think Liquid Projections is the right place to handle this issue. It should be handled in NEventStore itself ideally. Otherwise it can be handled in a decorator for IPersistStreams.