Follow-up from "Security Dashboard API hookup"

We need seperate error states on the dashboard for each endpoint failure.

Currently, if either of them fail the whole dashboard is replaced with an error state.

#6709 (closed)

The following discussion from !7793 (merged) should be addressed:

currently, a failure from either the counts or the list will trigger the same error state. I'm not too sure this is the best approach though now that I think about it. Maybe only the list should trigger the error state and the counts could have a seperate one.

Correct this is not optimal. We want the page to be available even if one of the data sets, (summary counts or vulnerability list) is not available for some reason. We currently don't have designs for this use case.

Edited by Sam Beckham