Crons: OK checkins after a in_progress has timedout should not be discarded

Imagine the following scenario:  The following has happened 1. **12:00**: A in_progress check-in is sent 2. **01:00**: The 1 hour user-configured timeout is reached and the check-in is marked as **`timed_out`** 3. **01:15**: An `ok` check_in is sent. In this scenario the users monitor is truly running longer than their configured timeout (The number of minutes a check-in is allowed to run before it's considered failed.). However, we are currently completely discarding the OK check in. ### What do we want to do? Some options - Update the check-in duration with the **true duration**. Right now we don't do this and timeouts just have no duration. (https://github.com/getsentry/sentry/pull/67303) - Create a new status such as `CLOSED_TIME_OUT`, which would represent a check-in that reached timeout state, but was also received a terminal check in after the fact that it was marked timed out. In this scenario it's also worth considering what would happen if the check-in after the timeout was a `error` or even a `timed_out`.