[PWGDQ] Save the information of ambiguous pairs

[yuanz-USTC]

Define histograms to save the information of mix event ambiguous pairs and also ambiguous pairs which are double counted for both same event and mix event.

[alibuild]

Error while checking build/O2Physics/o2 for 8d48489 at 2025-04-02 16:24:

## sw/BUILD/O2Physics-latest/log
/sw/SOURCES/O2Physics/10733-slc9_x86-64/0/PWGDQ/Tasks/tableReader_withAssoc.cxx:1762:37: error: 'iPairs' was not declared in this scope; did you mean 'iPair'?
/sw/SOURCES/O2Physics/10733-slc9_x86-64/0/PWGDQ/Tasks/tableReader_withAssoc.cxx:1765:35: error: 'iPairs' was not declared in this scope; did you mean 'iPair'?
/sw/SOURCES/O2Physics/10733-slc9_x86-64/0/PWGDQ/Tasks/tableReader_withAssoc.cxx:1957:35: error: 'iPairs' was not declared in this scope; did you mean 'iPair'?
/sw/SOURCES/O2Physics/10733-slc9_x86-64/0/PWGDQ/Tasks/tableReader_withAssoc.cxx:1960:33: error: 'iPairs' was not declared in this scope; did you mean 'iPair'?
ninja: build stopped: subcommand failed.

Full log here.

[alibuild]

Error while checking build/O2Physics/o2 for bd3a358 at 2025-04-28 15:09:

No log files found

Full log here.

[github-actions]

O2 linter results: ❌ 199 errors, ⚠️ 0 warnings, 🔕 0 disabled

[iarsene]

Here you create a vector of composite cuts, but you actually just need the name of the cuts. So I suggest to make a vector of TString only.

[iarsene]

If you get the vector of cuts at this point, then this would mix-up the track bits and corresponding histogram directories. The problem is that these are the track cuts specified in the same event pairing configurable. This is not guaranteed to be in the same order (or they don't even exist in the track-selection task) as the cuts actually defined in the track selection task. As you see later in the init and the run function, for the track bits, we rely on the order in which the user provided the cuts in the track-selection task, not in this task. So I think its probably enough to actually initialize this vector a bit lower in the init function, where we loop over the track cuts defined in the track-selection task and check if these where required in the same-event-pairing task.