Implement a solo block-nodes deploy command/sub-command.

• needs to run prior to solo network deploy
• install the block-node-server Helm Chart
  • disable kubepromstack in our <solo-root>/resources/block-nodes-values.yaml
  • disable loki in our <solo-root>/resources/block-nodes-values.yaml
  • disable promtail in our <solo-root>/resources/block-nodes-values.yaml
  • use the resources and blockNode settings from https://github.com/hiero-ledger/hiero-block-node/blob/main/charts/block-node-server/values-overrides/mini.yaml in our <solo-root>/resources/block-nodes-values.yaml but use JAVA_OPTS: "-Xms8G -Xmx8G"
• add the following flags:

--chart-version
--cache-dir # not sure if this is needed, leave it out if not used
--chart-dir
--cluster-ref
--deployment
--dev
--domain-name
--enable-ingress
--quiet-mode
--values-file

• ensure the Block Nodes components are running and ready, we can use the following health checks: /healthz and /readyz.
• set the nameOverride in the <solo-root>/resources/block-nodes-values.yaml to include the ID of this Block Node, perhaps bn-0 for ID=0. The ID will start at zero and increment by one. NOTES: there can be more than one block node, and in larger environments there most likely will be more than one. If one is deleted, that index should never be used again, even if it is the highest index number. Which means we should have a next block node ID stored in the remote config, and to be used to set this block node ID. An issue will be created to do something similar for the consensus node, mirror node, explorer, and relay; as they also can have more than one and need to track next available.

NOTE: reach out to Slack@Fredy for any Block Nodes related questions

• required by update solo network deploy to conditionally create the /opt/hgcapp/services-hedera/HapiApp2.0/data/config/block-nodes.json #1757