feat(dependecy-track): interpolated project name

[migmartri]

Enables annotations interpolation (#252) in the Dependency-Track plugin.

Now, during attachment, the project name can contain material annotations that will be resolved before pushing to the dep-track instance.

For example, let's say that you have the following contract with two SBOMs and a component annotation (note that the value of the annotation is set in the contract but it is also now possible to set it at runtime #281)

{
  "schemaVersion":  "v1",
  "materials":  [
    {
      "type":  "SBOM_CYCLONEDX_JSON",
      "name":  "controlplane-sbom",
      "annotations":  [
        {
          "name":  "component",
          "value":  "controlplane"
        }
      ]
    },
    {
      "type":  "SBOM_CYCLONEDX_JSON",
      "name":  "cas-sbom",
      "annotations":  [
        {
          "name":  "component",
          "value":  "cas"
        }
      ]
    }
  ]
}

This annotation can then be set during attachment.

chainloop integration attached add ... --opt projectName="miguel-test-{{.Material.Annotations.component}}

The result of this at execution time would be sending

• controlplane-sbom => miguel-test-controlplane
• cas-sbom => miguel-test-cas

Some notes about the implementation

• Adding templates in the project name is optional, using static names is also supported (current behavior)
• At attachment time we check if the template in the project name is valid
• At execution time, if we can't find the annotation in one of the SBOMs, we skip it.

[migmartri]

this is the new part.

[migmartri]

and this validation at attachment time

[danlishka]

LGTM