Str: Silence predicted chi2 calculation

[f3sch]

Around 60-70% of the async logs are polluted by the strangeness trackers update step with negative values which is of little help.
Also the abs of the chi2 is taken afterward so the logged message is by definition ignored thus silencing it just follows this logic.

[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

[f3sch]

@fmazzasc would this be fine for you?

[fmazzasc]

Yes, it makes sense to me. Thank you!

[f3sch]

@shahor02 is it also fine for you, if so please merge?

[shahor02]

I cannot say that I like to accept negative chi2's quietly, but let's have it merged now. Eventually, if we don't manage to avoid bad cov.matrices, we should either redefine the cov.matrix to have chi2 positive, we should at kill the cluster.