feat: show manifests in image list

[cdrage]

feat: show manifests in image list

What does this PR do?

• Shows manifest in the image list
• Does NOT show any actions / be able to click (yet)
• Allows you to click and view details.

Screenshot / video of UI

Screen.Recording.2024-05-21.at.11.06.01.AM.mov

What issues does this PR fix or reference?

Closes #6529
Closes #7255

How to test this PR?

• Tests are covering the bug fix or the new feature

1. Create a manifest through the GUI or podman build --platform linux/arm64,linux/amd64 --manifest testmanifest123
2. View the manifest in image list.

Signed-off-by: Charlie Drage charlie@charliedrage.com

[cdrage]

FYI it is intentional that there are no actions shown / unable to click for more details / no delete button. As those are in separate PR's in the epic: #6526 specifically issues: #7041 and #7181

[deboer-tim]

I think it's curious/annoying that manifests are images in the API, and makes it so that something like ImageColumnActions needs to be shared. :-/

I think this is a good place to go with the first PR, but:

• In the containers view we have "my-pod (pod)", but here you used a badge. We obviously didn't have badges when we did the containers view, but I think we need to decide with design the right way to identify 'different things in a table' is and make them consistent. For simplicity/consistency maybe I'd rather use '(manifest)' until we know.
• The icon should be different from a regular image.
• Manifests should have details pages (but can be a separate issue).
• We should allow them to expand/collapse with the images that are in them, but that is post Table component support for parent/children #7209.

I don't want to hold this up too much, but I think we should at least have a direction on 1/2 and issue for 3 before we merge.

[cdrage]

I think it's curious/annoying that manifests are images in the API, and makes it so that something like ImageColumnActions needs to be shared. :-/

I think this is a good place to go with the first PR, but:

• In the containers view we have "my-pod (pod)", but here you used a badge. We obviously didn't have badges when we did the containers view, but I think we need to decide with design the right way to identify 'different things in a table' is and make them consistent. For simplicity/consistency maybe I'd rather use '(manifest)' until we know.
• The icon should be different from a regular image.
• Manifests should have details pages (but can be a separate issue).
• We should allow them to expand/collapse with the images that are in them, but that is post Table component support for parent/children #7209.

I don't want to hold this up too much, but I think we should at least have a direction on 1/2 and issue for 3 before we merge.

I totally agree, let's talk about it in the UX call. There are a lot of other missing pieces that should be worked on before we merge the "showing in list" support.

For this PR I will:

• Add (manifest) similar to (my-pod) instead of a badge
• Different icon (will ask you or @ekidneyrh on advice what we should do)

I thought I had opened a "details" issue for manifest, but I had not. I've opened up issue #7255 and added it to the epic #6526

Maybe we should keep this as draft / WIP until we get the details page in too so we at least have the basic functionality of manifests.

[cdrage]

This PR is ready for review with the exception of the new icon being added, which can be in a follow up PR.

I've made the following changes:

• New folder / files, based on how we do ImageDetails.svelte
• Added a BASIC manifest summary page, a more advanced summary page based on using inspectManifest will be added via issue: Manifests "more in depth" details page. #7270
• Added tests

[lstocchi]

Tested and works as described. LGTM

[cdrage]

Manifest icon has now been added and this PR is ready for another review @lstocchi @deboer-tim

[deboer-tim]

LGTM, worked well in testing.