Anomaly strict

Work towards #1300 
Currently implements that also "predicted but not found" patterns contribute to anomaly score. 

TODO:
- [ ] 1/ change Anomaly class to take array of columns' permanences as input
- [ ] 1.2/ Then anomaly class can be a stateful machine and can take only 1 argument (actual permances) and and keep track of the "prevPredictedColumns" itself.
- [ ] 2/ revert `computeRawAnomalyScore` back and add a new `MODE_` for the new anomaly, vs. having the one and only anomaly computation method?
- [ ] 3/ use only the true predicted columns (permanence>=threshold) as "predicted" columns.

Please let me know what you think about the TODO items. 
:1234: