ci: add container scanning to default checks

[zondervancalvez]

Trivy is a cutting-edge security tool designed to enhance the safety of containerized applications by conducting thorough vulnerability assessments. Specifically developed for scanning container images, ranging from low-severity issues to critical threats. It employs an intelligent rating system to categorize vulnerabilities based on their severity levels, ensuring that high to critical vulnerabilities are given special attention. Upon detecting vulnerabilities that fall within this elevated range, Trivy will throw an error.

By integrating Trivy into our deployment pipeline, we can proactively mitigate security risks and enhance the resilience of our repository.

Fixes #1876

Depends On: #2865
Depends On: #2864
Depends On: #2863
Depends On: #2862

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[petermetz]

@zondervancalvez ^^ Please see @jagpreetsinghsasan 's comment above!

[petermetz]

@zondervancalvez Please enable the trivy scanning for the production images (right now I see some AIO test images that are being tested that we can omit and save resources - but I also see one or two of the production images listed below that do not have the trivy scan added)

ghcr-cmd-api-server
ghcr-connector-besu
ghcr-connector-corda-server
ghcr-connector-fabric
ghcr-keychain-vault-server

[petermetz]

@jagpreetsinghsasan Have your review points been addressed? I think I saw that the trivy checks are now part of the same job that builds the container so there is no duplicate builds being performed.

[jagpreetsinghsasan]

LGTM now

[petermetz]

@jagpreetsinghsasan Great, thank you!
@zondervancalvez Please resolve the merge conflicts and pass it back for review and then we can merge!