Traffic not updating to most recent revision

As detailed in this Teams thread, we have seen occurrences of traffic not being directed to the the most recent cloud run revision as part of a deployment. The theory is that at some point traffic was directed to a specific revision via a manual update in the GCP console, and then the traffic attribute was never updated by terraform to point back to the most recent revision.

The impact has been resolved in the Research Dashboard project, but if we see this occur elsewhere we should set the default traffic value to <code data-sourcepos="3:144-3:182">TRAFFIC_TARGET_ALLOCATION_TYPE_LATEST</code> at 100% as has been done for Research Dashboard.