Allow tweaking the name of vulnerability scan containers by exposing prefix/suffix param string

[alifib]

Issue: vulnerability scan containers are currently created named exactly like the containers being scanned.
Although these containers are within pods in (possibly) another namespace, they are easily mistaken to be the actual containers when observed (e.g. in log aggregation systems like Grafana).

Requested solution: Allow specifying a prefix or suffix string that would be appended to the container name to differentiate it from the target container being scanned.