fix: use fullname helper for resource-config ConfigMap name

The resource-config ConfigMap uses a hardcoded name instead of the
portkeyenterprise.fullname helper. This causes a name collision when
deploying multiple chart instances in the same namespace — all instances
try to own the same ConfigMap, causing ArgoCD sync conflicts.

- Prefix name with portkeyenterprise.fullname (consistent with all
  other resources in the chart)
- Add standard chart labels via portkeyenterprise.labels
- Update values.yaml comment and README to reflect dynamic naming

Author: Campbell Pool

charts/portkey-gateway/README.md

@@ -330,7 +330,7 @@ MONGO_GENERATION_HOOKS_COLLECTION_NAME: "<Mongo Collection for Hooks>"
 volumes:
 - name: shared-folder
   configMap:
-    name: resource-config
+    name: <release-fullname>-resource-config  # e.g. my-release-gateway-resource-config
 volumeMounts:
 - name: shared-folder
   mountPath: /etc/shared/document_db.pem

charts/portkey-gateway/templates/resources-config.yaml

@@ -1,7 +1,9 @@
 apiVersion: v1
 kind: ConfigMap
 metadata:
-  name: resource-config
+  name: {{ include "portkeyenterprise.fullname" . }}-resource-config
+  labels:
+    {{- include "portkeyenterprise.labels" . | nindent 4 }}
 data:
   document_db.pem: |
     -----BEGIN CERTIFICATE-----

charts/portkey-gateway/values.yaml

@@ -264,7 +264,8 @@ autoscaling:
 volumes: []
 # - name: shared-folder
 #   configMap:
-#     name: resource-config
+#     # Use your release's fullname: kubectl get configmap -l app.kubernetes.io/managed-by=Helm
+#     name: my-release-gateway-resource-config
 
 # Additional volumeMounts on the output Deployment definition.
 volumeMounts: []