Add updated performance report

[glpuga]

Proposed changes

This PR adds a new performance report, since the latest one predates important performance enhancing changes in the code.

This PR also identified #253 and had to circumvent it to make the actual capture of metrics.

This results need to be independently replicated before merging. The results are out of line with the latest results for a similar code version, and I've don't have a full explanation for the differences (see #233 )

Type of change

• 🐛 Bugfix (change which fixes an issue)
• 🚀 Feature (change which adds functionality)
• 📚 Documentation (change which fixes or extends documentation)

Checklist

Put an x in the boxes that apply. This is simply a reminder of what we will require before merging your code.

• Lint and unit tests (if any) pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• All commits have been signed for DCO

[glpuga]

@hidmic @nahueespinosa since these results are so much different from the latest ones we got, and I can't really explain all the differences, this needs to be thoroughly reviewed and replicated before merging.

[glpuga]

Forget about it.

The launch files are broken, all the measurements were using the same configuration, that why beam model looks to good, and yet so similar to likelihood.