Content Copy / Content Sync should preserve published state and support scheduled, scalable Author→Author+Publish sync

AEM as a Cloud Service "Copy Content" copies author-tier content only and intentionally strips replication-status metadata (cq:lastReplicated, cq:lastReplicationAction, cq:lastReplicatedBy, incl. the _publish/_preview variants). As a result, after a Prod→Stage copy the destination author has no record of what was published on the source, and nothing is published on the destination's publish tier.

The only way teams can reproduce the source's published state today is to build external tooling that:
1. queries the source (Prod) for the full activated set (e.g. via QueryBuilder), then
2. re-replicates exactly that set on the target (Stage), chunk by chunk.

This is inefficient by construction — it re-derives state the source environment already holds, it's bounded by QueryBuilder-over-HTTP result limits and request timeouts, and it doesn't scale to large
repositories (millions of nodes / multi-TB). We built and open-sourced such a tool to prove it works — https://github.com/rwunsch/aem-content-sync — but the fact that every customer has to build this is
the problem: it's redoing work the Content Copy tool itself should do.

Requested:
- An option to preserve replication status through Content Copy, and/or
- Auto-publish copied content on the target (so the destination publish tier matches the source), and
- Make these schedulable and scalable (delta/incremental, resumable), so lower environments can be kept in sync unattended without external scripts.

This would eliminate a whole class of brittle, slow custom tooling and make environment refreshes accurately reflect production's published state.