* test: score time in mesh
* add TestScoreFirstMessageDeliveries
* rm redundant initialization to zero
* add TestScoreFirstMessageDeliveriesCap
* add TestScoreFirstMessageDeliveriesDecay
* fix comment
* add TestScoreMeshMessageDeliveries
* comments
* add TestScoreMeshFailurePenalty
* add TestScoreInvalidMessageDeliveries
also, TestScoreInvalidMessageDeliveriesDecay
* add TestScoreApplicationScore
* add TestScoreIPColocation
* add TestScoreMeshMessageDeliveriesDecay
* add TestScoreRetention
* try longer interval for TimeInMesh test
we seem to take longer to collect the score on travis,
which causes the score to be outside the expected bounds.
hopefully a longer wait time will give us more wiggle room.
Co-authored-by: Yusef Napora <yusef@protocol.ai>
Yusef Napora
dirkmc