The previous commit (perf(tree): use LakeFS path-filtered logCommits ...)
relies on the ``objects=`` / ``prefixes=`` / ``limit=`` query parameters on
``logCommits``, introduced in LakeFS v0.54.0 (released 2021-11-08).
Pre-v0.54 servers silently ignore those parameters and would surface
incorrect ``lastCommit`` metadata on the file-list ``expand=true`` page.
The shipped docker bundle pins ``treeverse/lakefs:latest`` so default
deployments are always compatible. The constraint only matters for
self-deployments that pin an older LakeFS image.
Document the requirement in:
* README — Architecture/Stack line and the Quick Start "Prereq" callout.
* docs/setup.md — new "Prerequisites" section.
* docs/deployment.md — new "Component Version Requirements" section.
* docs/deployment/production.md — new "Component Versions" section.
* docs/deployment/docker.md — extended ``lakefs`` service description.
Code-side docstrings on ``LakeFSRestClient.log_commits`` and
``tree.resolve_last_commits_for_paths`` already carry the same note from
the original perf commit.
