[Feature](lance) Support time travel and REST managed versioning

## Parent

Tracked by #66340. The baseline Lance read integration was introduced by #65730.

## Scope

- [ ] Support time travel and explicit dataset version selection.
- [ ] Support REST Namespace managed versioning in the BE reader.
- [ ] Keep schema binding, fragment planning, and scan execution on the selected version.
- [ ] Define errors for missing, expired, or inaccessible versions.

## Completion criteria

- [ ] FE and BE implementation is complete.
- [ ] Unit and regression tests cover explicit versions, timestamps, and REST-managed versions.
- [ ] User documentation describes syntax, semantics, and limitations.
- [ ] The capability is verified with representative filesystem and REST Namespace datasets.

Start by reviewing the baseline Lance read integration from #65730 and the parent work in #66340, then trace the FE and BE reader entry points. Define how explicit versions, timestamps, and REST Namespace managed versions flow through schema binding, fragment planning, and scan execution. Done means implementation, unit and regression tests, documentation, and verification on filesystem and REST Namespace datasets.

Written by the indexing model from the issue text.