fix(build): check for CVEs before merge

[domsolutions]

Motivation

Currently we have to merge PRs and then trigger a release and push images to docker hub to then scan them for CVEs. This is quite dangerous as we could be merging unsafe code and also causes long feedback loop, to know if a change has introduced a CVE.

Summary of changes

• Within github workflow V1 Security Tests we now build the images but do not push to a repo, and scan with snyk
• Upgraded base images to use latest registry.access.redhat.com/ubi9/ubi-minimal:9.6, removed the latest tag which would have achieved the same thing, but it's safer and gives a better audit trail to specify a specific tag.
• upgrade rlcone to latest version - there is now only one high CVE but there has not been a released fix yet so this is not fixable.

NOTE

Commented out building/scanning Alibi Detect as GH runner runs out of disk space. It is possible to build the image locally as we push the base image up to GH artifactory but not ideal. Potentially look at using private GH runner.

Checklist

• Added/updated unit tests
• Added/updated documentation
• Checked for typos in variable names, comments, etc.
• Added licences for new files

Testing

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.