feat: add support for new tools object format from CycloneDX 1.5

[mmarseu]

This PR adds support for transforming SBOMs using CycloneDX 1.5's new .metadata.tools object.

If the SBOM

• uses the now-deprecated array style, it will stay an array.
• uses the new object style, it will stay an object.
• contains no .metadata.tools field, an array will be created.

[github-actions[bot]]

Coverage Report •

File	Stmts	Miss	Cover	Missing
auxiliary
output.py	54	1	98%	97
sbomFunctions.py	140	3	97%	70, 78, 155
TOTAL	1448	55	96%

Tests	Skipped	Failures	Errors	Time
270	0 :zzz:	0 :x:	0 :fire:	3.716s :stopwatch:

[italvi]

If the SBOM

• contains no .metadata.tools field, an array will be created.

Is this really according to our discussion in #142? Would not be the proper check if sbom.get("specVersion","") < 1.5 then list else dict?

[mmarseu]

If the SBOM

• contains no .metadata.tools field, an array will be created.

Is this really according to our discussion in #142?

Not at all. But it was an easy solution which works fine until the array version is removed from the spec (not before CycloneDX 2.0, I imagine, as that would be a breaking change).

Would not be the proper check if sbom.get("specVersion","") < 1.5 then list else dict?

Well, in real, non-pseudo code, this was a little harder to do, but it is done 😉