use startFrom when listing blobs from OneLake endpoints

There's an issue when using startFrom with OneLake endpoints (see #695).
We have disabled this optimization for OneLake endpoints in #696
Once its fixed on the OneLake side, we can re-enable this optimization. This is a tracking issue to reenable.

We were able to fix this on the OneLake side. Closed the workaround PR #696 and this issue is no longer needed