feat: add BomRefs for known models according to CycloneDX 1.5

[jkowalleck]

Changed

• getter model.contact.PostalAddress.bom_ref may no longer return None

Added

• Class model.contact.OrganizationalContact supports bom_ref
• Class model.contact.OrganizationalEntity supports bom_ref
• Class model.license.DisjunctiveLicense supports bom_ref
• Class model.license.LicenseExpression supports bom_ref

---

TODO / DONE

• add missing bom_ref properties

---

• fixes feat: add bom-ref to known models according to spec #856
• fixes model.contact.OrganizationalEntity missing bom_ref attribute #799

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.05%	✅ 100.00% (target: 80.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (5621705)	5642	5281	93.60%
Head commit (d356f73)	5684 (+42)	5323 (+42)	93.65% (+0.05%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#859)	47	47	100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

[jkowalleck]

Note

❗ to be discussed: is this a breaking change?

• yes: the serialization result might change (be no longer reproducible) in case no bom-refs are set for the data models that gained this capability.
• no: all interfaces stayed stable, no required parameters were added, etc...

[jkowalleck]

Note

❗ to be discussed: is this a breaking change?

* yes: the serialization result might change (be no longer reproducible) in case no bom-refs are set for the data models that gained this capability.

* no: all interfaces stayed stable, no required parameters were added, etc...

rolled back the following changes, to make the feature a non-breaking one:

• All known BomRefs for model classes are autopopulated when deserializing.
• All known BomRefs for model classes are properly discriminated when deserializing.