Currently, when the UI is loading data from the API server, it gives no indication to the user that it is performing XHR. This would prevent the UI from flashing when the user first logs in (first the UI is rendered, then async call(s) containing the server data are resolved, and the UI is re-rendered to display the new data).

Third-party modules already exist to handle this type of asynchronous loading, so we would not necessarily add much code to provide this mechanism.

The only big concern here is that the "auto-refresh" functionality might break as a result of this change. Since we plan to handle this with WebSocket, we may need to do this ticket after that work has been completed.

This ticket is complete when unresolved asynchronous loads are indicated in the UI.