add support for comma separated values in runtime annotations

[mluedke]

No description provided.

[blacksd]

We need to think this through a little bit more; what if we define multiple workload names w on multiple namespaces n - do we need to parse the n*m possibilities?
I think we need to stick to something that is able to address directly the kind of use we want to make for every annotation. Do I need to identify a name in a cloud provider? Those should be the only informations entered.

[Jujuyeh]

This is an interesting discussion but it seems that customers are finding that their Components (or equivalent Entities) sometimes have complex mappings. For this purpose I added the sysdigcloud.com/custom-filter annotation; but it seems one will not be enough, as it overrides all annotations (for all sections).

So my takeaways are:

• Introduce @mluedke changes as they don't break past behavior and also provide a solution for these complex mappings. I will add your commits in the 1.2.0 release PR, so we can close this PR. Add custom backlink settings and multiple values for Runtime VM annotations [1.2.0] #10
• I will introduce in the future if necessary additional sysdigcloud.com/custom-filter-* scoped to only override specific sections (VM Runtime, VM Registry, VM Pipeline, Inventory)