[PWGHF] Reduce code duplication in the treeCreatorLcToPKPi

[lubynets]

Such common parts as:

• filling event properties;
• tables size reservation;
• filling Lite, Full and KF tables;
• candidate's invariant mass evaluation

used both an MC and Data oriented functions were encapsulated in separate functions.

The treeCreatorLcToPKPi's output was checked before and after the PR changes in the following conditions: MC and Data; DCAFitter and KFParticle; Lite and Full table. In all 2×2×2=8 cases there was the byte-to-byte size match of produced AnalysisResults_trees.root files before and after PR.

[github-actions]

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

[mfaggin]

Hi @lubynets , from a quick look your proposals look good to me. If it is fine with you, I'd just ask you to wait for this PR here #10984 which introduces a massive development in the framework. If it is fine with you, I'd ask you to wait for it and rebase on it, before merging yours.

[lubynets]

Hi @lubynets , from a quick look your proposals look good to me. If it is fine with you, I'd just ask you to wait for this PR here #10984 which introduces a massive development in the framework. If it is fine with you, I'd ask you to wait for it and rebase on it, before merging yours.

Hi @mfaggin, yes, it's fine with me to wait until another PR is merged.

[lubynets]

Hi @mfaggin,
As I see the PR 10984 was merged.
Should I really rebase my branch with master (that will require force push), or merge master into my branch will be also ok? In both cases there will be conflicts, however I already addressed them in merge mode. The only thing which I am concerned of is that after git merge, my PR will pretend to have plenty of changes which were done neither by me nor by you in your PR, that may trigger all possible PWGs and assign all possible labels (?)...
Here is the clone of my branch after git merge master and resolving a conflict https://github.com/lubynets/O2Physics/commits/tlc_merge/ Is it ok if I do the same with the source branch of my PR?

[vkucera]

As long as you don't modify the commits merged from upstream, they will not appear in your PR.

[lubynets]

Dear @mfaggin (@vkucera cc),
I updated my PR according to the master branch. Could you please have a look at it?

[mfaggin]

thanks @lubynets , approved