modify k3d-dev.sh to use ib metallb images

This modifies k3d-dev.sh to use the MetalLB images from Iron Bank per #1804 (closed). An implication of this change is that registry1 credentials are now required with to run k3d-dev.sh with MetalLB.

docs/assets/scripts/developer/metallb/kustomization.yaml

+resources:
+  - https://raw.githubusercontent.com/metallb/metallb/v0.13.12/config/manifests/metallb-native.yaml
+
+images:
+  - name: quay.io/metallb/controller
+    newName: registry1.dso.mil/ironbank/opensource/metallb/controller
+    newTag: v0.13.12
+  - name: quay.io/metallb/speaker
+    newName: registry1.dso.mil/ironbank/opensource/metallb/speaker
+    newTag: v0.13.12
+
+patches:
+  - target:
+      kind: Deployment
+      name: controller
+    patch: |-
+      apiVersion: apps/v1
+      kind: Deployment
+      metadata:
+        name: controller
+      spec:
+        template:
+          spec:
+            imagePullSecrets:
+              - name: registry1
+            securityContext:
+              fsGroup: 65532
+              runAsNonRoot: true
+              runAsUser: 65532
+              runAsGroup: 65532
+  - target:
+      kind: DaemonSet
+      name: speaker
+    patch: |-
+      apiVersion: apps/v1
+      kind: DaemonSet
+      metadata:
+        name: speaker
+      spec:
+        template:
+          spec:
+            imagePullSecrets:
+              - name: registry1
+            securityContext:
+              fsGroup: 65532
+              runAsUser: 0
+