Extend the timeout for flaky as slowness of the machine and add logs for TestRoutingTableProviderFromCurrentStates

  1. After cluster verification - logs when rebalance completes
  2. Waiting for routing table update - logs when waiting for MASTER assignment
  3. If update fails - logs what instances are actually present
  4. After participant shutdown - logs which node was stopped
  5. After cluster stabilization - logs when verify passes
  6. Before validation steps - logs which step is running
  7. If routing tables don't match - logs ideal state partitions

Now when it fails in CI, you'll see detailed logs like:
  INFO: Cluster verified after rebalance
  INFO: Waiting for routing table to update for partition TestDB-0
  INFO: Target node with MASTER: localhost_12918
  INFO: Shutdown participant: localhost_12918
  INFO: Waiting for cluster to stabilize after shutdown
  INFO: Cluster verified after shutdown
  INFO: Validate after step 4
  ERROR: Routing tables did not match between EV and CS providers
  ERROR: IdealState partitions: [TestDB-0, TestDB-1, ...]