Cleaner UI failure when run exists but resolution doesn't

[augray]

Very rarely, it is possible to end up in a state where a run exists, but a corresponding resolution does not. This is because the root run gets created before the resolution, so any error (ex: server unavailability) that happens between creation of the root run and creation of the resolution can leave us in this state. When this happens, the UI shows the run as an option on the run list, but when you visit the run page you get a blank page. Ideally we would be able to show the run, but just not show the things that require the resolution. An example run in this state can be found here:

https://josh.dev-usw2-sematic0.sematic.cloud/runs/7008e8b57c3b40c4a879fa80dd9c0fec

Here is an example of the UI for this run, as well as the network output. The first 7008e8b57c3b40c4a879fa80dd9c0fec corresponds to getting the run, and is successful. The 404 7008e8b57c3b40c4a879fa80dd9c0fec corresponds to getting the resolution, which does not.