Refactor anomaly score computation

[lorenzomammana]

Summary

Describe the purpose of the pull request, including:

Change the way anomaly scores are normalized by default, instead of using a [0-1] range with a 0.5 threshold, the scores are now normalized to a [0-1000] range with a threshold of 100, the new score represents the distance from the selected threshold, for example, a score of 200 means that the anomaly score is 100% of the threshold above the threshold itself, a score of 50 means that the anomaly score is 50% of the threshold below. This change is intended to make the scores more interpretable and easier to understand, also it makes the score independent from the min and max
scores in the dataset.

Type of Change

Please select the one relevant option below:

• Breaking change

Checklist

Please confirm that the following tasks have been completed:

• I have tested my changes locally and they work as expected. (Please describe the tests you performed.)
• I have added unit tests for my changes, or updated existing tests if necessary.
• I have updated the documentation, if applicable.
• I have installed pre-commit and run locally for my code changes.