Bug: `TrajectoryAnalyzer` miscenters pooled batches under PBC (`batch_size > 1` / `-1`)

[gtaillandier]

TrajectoryAnalyzer appears to miscenter pooled batches under PBC when using TemporalAggregator(batch_size > 1) or batch_size = -1.

• batch_size=1: OK
• batch_size>1 / -1: pooled frames can mix periodic images, distorting the interface and biasing fitted contact angles.

This seems specific to TrajectoryAnalyzer (separable pipeline). Coupled analyzers are likely unaffected because they use a different pooled-density fitting path.

Requested fix: apply PBC-aware recentering per frame before concatenation in pooled TrajectoryAnalyzer execution, and add a regression test comparing batch_size=1 vs >1/-1 on a wrapped/drifting trajectory.

[gtaillandier]

Problem solved but remaining there is one issue remaining, is the lack of translation on the COM for the wall explicit given in the case of the use for the wall detector of an explicit wall