[v1.13] correct z positions of hits for RP (#1444)

### Briefly, what does this PR introduce?

Fix bug in old positions for RP sensors in EICrecon.

### What kind of change does this PR introduce?
- [x ] Bug fix (issue #__)
- [ ] New feature (issue #__)
- [ ] Documentation update
- [ ] Other: __

### Please check if this PR fulfills the following:
- [ x] Tests for the changes have been added
- [ ] Documentation has been added / updated
- [ ] Changes have been communicated to collaborators

### Does this PR introduce breaking changes? What changes might users
need to make to their code?

No.

### Does this PR change default behavior?

Yes - this will make RP tracks work again.

Co-authored-by: Alexander Jentsch <[email protected]>
(cherry picked from commit f9ad494)

Co-authored-by: Alex Jentsch <[email protected]>

src/detectors/RPOTS/RPOTS.cc

@@ -61,10 +61,10 @@ void InitPlugin(JApplication *app) {
     recon_cfg.local_y_slope_offset = -0.0451035;  // in mrad
     recon_cfg.nomMomentum          =  275.0;      // in GEV --> exactly half of the top energy momentum (for proton spectators from deuteron breakup)
 
-    recon_cfg.hit1minZ = 25099.0;
-    recon_cfg.hit1maxZ = 26022.0;
-    recon_cfg.hit2minZ = 27099.0;
-    recon_cfg.hit2maxZ = 28022.0;
+    recon_cfg.hit1minZ = 32541.0;
+    recon_cfg.hit1maxZ = 32554.0;
+    recon_cfg.hit2minZ = 34239.0;
+    recon_cfg.hit2maxZ = 34252.0;
 
     recon_cfg.readout              = "ForwardRomanPotRecHits";