Improve generation of base images SBOMs

[mkosiarc]

most functional changes are in the related PR that updates the
base_images_sbom_script.py
konflux-ci/build-tasks-dockerfiles#191

Here, we are just updating on how we generate the inputs for this
script.
We are now passing the whole parsed Dockerfile in json format to that
script, which allows us to better parse/detect base images.

Also, the format of the /shared/base_images_digests file was changed.
Previously we could rely on the order of the image references with the
digests in the file. Now we need to provide a mapping from an image
reference as it was used in the Dockerfile to the full image reference
with digests that was used during build and generated by buildah.

The mapping is done as:

Also, the sbom utility image has to be updated together in the same
PR/commit, otherwise it would break konflux temporarily

KFLUXBUGS-1718

[mkosiarc]

has to be merged only after konflux-ci/build-tasks-dockerfiles#191

[chmeliik]

<image-reference-used-in-dockerfile>|<full-image-reference-with-digest>
The character that creates the mapping "|" was chosen arbitrarily, just
because it cannot be a valid part of image reference.

It would be a bit more natural to just separate them by whitespace, but this is OK too

[mkosiarc]

<image-reference-used-in-dockerfile>|<full-image-reference-with-digest>
The character that creates the mapping "|" was chosen arbitrarily, just
because it cannot be a valid part of image reference.

It would be a bit more natural to just separate them by whitespace, but this is OK too

I guess I don't mind using space instead of "|". I just used it for more visibility and because of an (possibly irrational) fear that additional empty space might find its way to the file, causing problems with the parsing.

[chmeliik]

<image-reference-used-in-dockerfile>|<full-image-reference-with-digest>
The character that creates the mapping "|" was chosen arbitrarily, just
because it cannot be a valid part of image reference.

It would be a bit more natural to just separate them by whitespace, but this is OK too

I guess I don't mind using space instead of "|". I just used it for more visibility and because of an (possibly irrational) fear that additional empty space might find its way to the file, causing problems with the parsing.

Python handles additional spaces without issues

In [1]: "   image1\t \t image2     \n".split()
Out[1]: ['image1', 'image2']

(and so does Bash, in fact)

$ read -r image1 image2 <<< $'   image1\t \t image2     \n'
$ echo "$image1; $image2;"
image1; image2;

[mkosiarc]

Yeah, like I said, it was more irrational :D I can make the switch to using space.

[mkosiarc]

/retest