EsentModel throwing 'Version store out of memory' when filling GeometryStore on large models

[andyward]

See https://github.com/xBimTeam/XbimGeometry/issues/514#issuecomment-2531994109 - where a complex Tekla model triggers a 'Version store out of memory (cleanup already attempted)' exception in Esent. See https://github.com/microsoft/ManagedEsent/issues/24

We need to establish if these models are an outlier, or if we need to adapt the algorithm (e.g. transaction batch size?) or if we need to review the parameters we initialise Esent with. e.g. MaxVerPages etc

See also #268