Fix backwards "Bouncing to" status

[jfongatyelp]

We've been reporting which version we are "Bouncing to" incorrectly for quite some time.

Old status:

paasta-contract-monitor.main in eksstage (EKS)
    Version:    5f01b83e (desired)
    State: Bouncing to configd345863a <--- reports the config version from "(old)" version
    Running versions:
      Rerun with -v to see all replicas
      5f01b83e, config6df36c8b (new) - Started 2024-11-26 12:29:06 (21 seconds ago) <--- most recent version, the one we are actually bouncing to
        Replica States: 10 Warming Up
      5f01b83e, configd345863a (old) - Started 2024-11-06 09:09:05 (20 days ago)

With my change:

paasta-contract-monitor.main in eksstage (EKS)
    Version:    5f01b83e (desired)
    State: Bouncing to config6df36c8b
    Running versions:
      Rerun with -v to see all replicas
      5f01b83e, config6df36c8b (new) - Started 2024-11-26 12:29:06 (now)
        0 pods found
      5f01b83e, configd345863a (old) - Started 2024-11-06 09:09:05 (20 days ago)
        Replica States: 3 Healthy / 7 Warning

This also fixes the tests to actually catch this behavior, and verify earlier/later timestamps get sorted the way we want.

[EvanKrall]

could also see just doing bouncing_to.append(versions[-1]....) if we want to keep newer versions on the bottom, but I don't particularly care which order the versions go in.

[EvanKrall]

could also see just doing bouncing_to.append(versions[-1]....) if we want to keep newer versions on the bottom, but I don't particularly care which order the versions go in.

oh wait this versions variable only seems to be used to calculate the bouncing_to version