Refactor noble cluster configurations to transition from the deprecated apps structure to a streamlined bootstrap approach. Update paths in various YAML files and README documentation to reflect the new organization under clusters/noble/bootstrap. This change enhances clarity and consistency across the deployment process, ensuring that all components are correctly referenced and documented for user guidance.

clusters/noble/bootstrap/cilium/README.md

@@ -14,7 +14,7 @@ helm repo update
 helm upgrade --install cilium cilium/cilium \
   --namespace kube-system \
   --version 1.16.6 \
-  -f clusters/noble/apps/cilium/values.yaml \
+  -f clusters/noble/bootstrap/cilium/values.yaml \
   --wait
 ```
 
@@ -25,7 +25,7 @@ kubectl -n kube-system rollout status ds/cilium
 kubectl get nodes
 ```
 
-When nodes are **Ready**, continue with **MetalLB** (`clusters/noble/apps/metallb/README.md`) and other Phase B items. **kube-vip** for the Kubernetes API VIP is separate (L2 ARP); it can run after the API is reachable.
+When nodes are **Ready**, continue with **MetalLB** (`clusters/noble/bootstrap/metallb/README.md`) and other Phase B items. **kube-vip** for the Kubernetes API VIP is separate (L2 ARP); it can run after the API is reachable.
 
 ## 2. Optional: kube-proxy replacement (phase 2)