Killing dagster jobs in the middle of crawling can cause issues

[C-Loftus]

If you kill a dagster job after it created a datastream but before the observations are inserting, that can leave the datastream in an ambiguous state.

• If a specific station is failing saying that the datastream does not have the phenomenonTime on the datastream that is a sign that the aforemention condition likely occured and as a result, the Thing object should be removed.
• While we could auto fetch the entire data if phenomenonTime is missing, it is in my opinion a good assertion for this to fail early to catch these sorts of edge cases.