`ReputationRecorder` tests are flaky

[t-bast]

I've seen this test fail a few times during CI:

ReputationRecorderSpec:

• basic attack *** FAILED ***
  java.lang.AssertionError: timeout 60 seconds expired
  at akka.testkit.TestKit$.poll$4(TestKit.scala:998)
  at akka.testkit.TestKit$.awaitCond(TestKit.scala:1006)
  at fr.acinq.eclair.reputation.ReputationRecorderSpec.$anonfun$new$9(ReputationRecorderSpec.scala:185)
  at fr.acinq.eclair.reputation.ReputationRecorderSpec.$anonfun$new$9$adapted(ReputationRecorderSpec.scala:173)
  at org.scalatest.FixtureTestSuite$TestFunAndConfigMap.$anonfun$apply$1(FixtureTestSuite.scala:275)
  at org.scalatest.OutcomeOf.outcomeOf(OutcomeOf.scala:85)
  at org.scalatest.OutcomeOf.outcomeOf$(OutcomeOf.scala:83)
  at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)
  at org.scalatest.FixtureTestSuite$TestFunAndConfigMap.apply(FixtureTestSuite.scala:275)
  at org.scalatest.FixtureTestSuite$OneArgTest$$anon$1.apply(FixtureTestSuite.scala:223)

[t-bast]

This test is also frequently failing:

MessageIntegrationSpec:

- automatically connect to known nodes *** FAILED ***
  java.lang.AssertionError: assertion failed: timeout (5 minutes) during expectMsgClass waiting for class fr.acinq.eclair.message.OnionMessages$ReceiveMessage
  at scala.Predef$.assert(Predef.scala:279)
  at akka.testkit.TestKitBase.expectMsgClass_internal(TestKit.scala:571)
  at akka.testkit.TestKitBase.expectMsgType(TestKit.scala:553)
  at akka.testkit.TestKitBase.expectMsgType$(TestKit.scala:552)
  at akka.testkit.TestKit.expectMsgType(TestKit.scala:973)
  at fr.acinq.eclair.integration.MessageIntegrationSpec.$anonfun$new$32(MessageIntegrationSpec.scala:375)
  at org.scalatest.OutcomeOf.outcomeOf(OutcomeOf.scala:85)
  at org.scalatest.OutcomeOf.outcomeOf$(OutcomeOf.scala:83)
  at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)
  at org.scalatest.Transformer.apply(Transformer.scala:22)

[thomash-acinq]

#3166 should fix it

[t-bast]

#3166 only fixes the ReputationRecorder test, please don't forget the MessageIntegrationSpec one as well in a different PR!