ImagesTable: Fix status bug

Fixes #899. The status of images (parent images and clones) in the
clones table was displayed incorrectly - the 'highest priority'
(e.g. failure > success) was displayed for all images.

This was due to a bug in a conditional in the ImageBuildStatus
component. In the main images table, rows for AWS images should display
the highest priority status of *all* images. A single failed clone
should cause the status of the row in the main images table to be
failure, even if the parent compose status is successful.

This logic was incorrectly being applied to *all* statuses. This commit
fixes this - from now on, this logic is only used for rows in the main
images table.

src/test/Components/ImagesTable/ImagesTable.test.js

@@ -497,7 +497,7 @@ describe('Images Table', () => {
         expect(row.cells[5]).toHaveTextContent('Expired');
       } else {
         renderWithProvider(
-          <ImageBuildStatus imageId={compose.id} />,
+          <ImageBuildStatus imageId={compose.id} isImagesTableRow={true} />,
           testElement,
           state
         );