feat: trivy vulnerability display

[jgrer]

• Created a new component, VulnerabilityDisplay, that functions similar to the docker scout vulnerability display.
• Separated the trivy scan and copa patch into two separate containers, so easier control of scans is possible.
• Created two new functions, triggerTrivy and runTrivy, that have a similar purpose to their copa variants
• Set the trivy container to have the name "trivy-copa-extension-container"
• Used this name to forcefully remove the previous trivy container when the users selects the "Scan Image" button
• Image selection is disabled when the user initiates a scan on an image
• Added new image, cat-tool, to dump the json output to stdout so the frontend can access it.

Closes: #11

[ashnamehrotra]

It looks like we can't go back and scan a new image if the most recently scanned image has no vulnerabilities. If it does, we are able to. We should fix that so users aren't blocked/forced to exit out of the extension to continue scanning.

[jgrer]

It looks like we can't go back and scan a new image if the most recently scanned image has no vulnerabilities. If it does, we are able to. We should fix that so users aren't blocked/forced to exit out of the extension to continue scanning.

as of now, this isn't reproducible. hopefully we can figure out if this was a bug in something on the local machine or an actual issue with the extension container