Add prefix to generated names for cluster-scoped configurations

Previously, resource names generated by the component library for
cluster-scoped configurations only used the target object name. This can
easily lead to name collisions. For example, OpenShift 4 has many CRs
named `cluster`.

This commit  adds code to use `<target.kind>-<target.apigroup>` as the
prefix when generating names for cluster-scoped configurations to reduce
the potential for collisions.

Author: simu

lib/resource-locker.libjsonnet

@@ -168,7 +168,20 @@ local rl_obj_name(objdata) =
   if objdata.namespace != null then
     '%s-%s' % [ objdata.namespace, name ]
   else
-    name;
+    // Reduce potential for name collisions when generating names for
+    // cluster-scoped ResourceLocker configurations.
+    local prefix =
+      if objdata.apigroup != '' then
+        '%s-%s' % [
+          std.asciiLower(objdata.kind),
+          std.strReplace(objdata.apigroup, '.', '-'),
+        ]
+      else
+        std.asciiLower(objdata.kind);
+    '%s-%s' % [
+      prefix,
+      name,
+    ];
 
 /**
  * \brief Create a managed resource (similar to Espejo, but for single NS)