TPC laser: add ccdp-populator path for laser replay run

[ehellbar]

No description provided.

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

[ehellbar]

@rmunzer this uses the proper CCDB upload path, depending on if it's synthetic data (replay) or not.

Another thing you would need to do for the laser replay is to adjust the QC jsons, which assume the run type to be LASER, but for the replay, we use the run type SYNTHETIC.