fix: Add persistent storage for aztec nodes in the spartan cluster

[stevenplatt]

This PR includes two changes:

• Adds persistent storage for Aztec nodes running the Spartan cluster
• Repairs previously merged load balancer configurations

Persistent Storage

Nodes that were previously configured with mounted volumes are now configured to use volumeClaimTemplates. Rather than directly configuring a PersistentVolumeClaim, a volumeClaimTemplate will automatically append index suffixes when replicas increase, so that there is not a storage conflict.

Persistent Storage for Grafana

The currently bundles Grafana instance uses a standard PersistentVolumeClaim since it is not expected to be deployed with replicas. Grafana also has an OS-level user defined it its container, which assumes ownership of the volume once it is mounted. To allow remounting, the user have to be defined in the helm chart. This is done using a securityContext in Grafana yaml template.

Repaired Load Balancer Config

PR #8786 previously made network interfaces either internal or external. This meant that when the network was set as public, certain references to internal network interfaces were no longer reachable. Specifically items that address a node port (bootNodeURL for example).

This PR adds the load balancer as a second interface, without modifying the original.

Testing

Code in this PR has been tested by by deployed the updated helm configurations to the Spartan cluster using command:

helm upgrade --install staging . -n staging --set network.public=true

As part of this change, replica counts have also validated to work without causing conflict for volume mounts, network interfaces or other resources.