exp/lighthorizon/build/index-batch: merge map/reduce updates to latest on feature branch

[sreuland]

PR Checklist

PR Structure

• [x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
• [x] This PR avoids mixing refactoring changes with feature changes (split into two PRs otherwise).
• [x] This PR's title starts with name of package that is most changed in the PR, ex. services/friendbot, or all or doc if the changes are broad or impact many packages.

Thoroughness

• [ ] This PR adds tests for the most critical parts of the new functionality or fixes.
• [ ] I've updated any docs (developer docs, .md files, etc... affected by this change). Take a look in the docs folder for a given service, like this one.

Release planning

• [ ] I've updated the relevant CHANGELOG (here for Horizon) if needed with deprecations, added features, breaking changes, and DB schema changes.
• [ ] I've decided if this PR requires a new major/minor version according to semver, or if it's mainly a patch change. The PR is targeted at the next release branch if it's not a patch change.

What

This is merging the net changes to map/reduce from #4501 to the latest on main feature branch, lighthorizon, which had changes merged from #4519 which refactored/consolidated related docker images.

Why

remove merge conflicts so net changes to map/reduce can be be committed, this PR represents the net changes needed from #4501 and deprecates need to merge that PR.

Known limitations