feat: add verbose mode for cves for image listing

[vrajashkr]

What type of PR is this?
feature

Which issue does this PR fix:
Towards #2175

What does this PR do / Why do we need it:
This PR introduces a new verbose output for listing CVEs for a given image. In this mode, all the details of the CVE are shown in full including the CVE Description and package related details.

Testing done on this change:

Will this break upgrades or downgrades?
No, there is no expected impact to upgrades or downgrades.

Does this PR introduce any user-facing change?:
Yes

A new --verbose flag is available for users to view complete details about the CVE impacting the image. This includes the full description and a list of packages which are vulnerable to the CVE.
The verbose mode can be invoked with bin/zli-linux-amd64 --config <config> cve list <image name> --verbose

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[vrajashkr]

This PR only adds the changes for the verbose mode. I'll create a separate PR for the changes to the non-verbose output.

[rchincha]

This is zli counterpart to the zui PR project-zot/zui#428?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.86%. Comparing base (2dd1fc9) to head (396cfca).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2307   +/-   ##
=======================================
  Coverage   92.86%   92.86%           
=======================================
  Files         166      166           
  Lines       21994    22023   +29     
=======================================
+ Hits        20424    20451   +27     
- Misses        977      979    +2     
  Partials      593      593           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[vrajashkr]

This is zli counterpart to the zui PR project-zot/zui#428?

It's slightly different as, per my understanding, zli never had a package listing at all before.

zui already had a package listing, but was missing the new PackagePath field.

[rchincha]

@vrajashkr there are linter failures.

[vrajashkr]

Yes, taking a look at it. Will update the PR once I get a chance.

[vrajashkr]

Branch was deleted due to an issue with pushing the updated. A fresh branch was created with the same changes and the lint issues resolved.