sudo solo-provisioner alloy cluster install doesn't respect --config file settings

### Bill of Materials, Application, or CLI Version

v0.24.0

### Describe the bug

The `alloy cluster install` command when used with `--config` including values below totally ignores the configured remotes. I had to run explicitly with flags:

First attempt:

```
sudo solo-provisioner alloy cluster install --config=/etc/solo-provisioner/config.yaml
```

Remotes were not populated.

Second attempt:

```
sudo solo-provisioner alloy cluster install --cluster-name=value --monitor-block-node --add-prometheus-remote="name=hashgraph,url=value,username=value,labelProfile=ops" --add-loki-remote="name=hashgraph,url=value,username=value,labelProfile=ops"
```

This worked, metrics began flowing.

Contents of '/etc/solo-provisioner/config.yaml`:

```yaml
profile: mainnet
blockNode:
namespace: "block-node"
release: "block-node"
chart: "oci://ghcr.io/hiero-ledger/hiero-block-node/block-node-server"
version: "0.38.1"
storage:
archivePath: /mnt/archive-storage/block-node/archive
archiveSize: 425Ti
livePath: /mnt/fast-storage/block-node/live
liveSize: 1Ti
logPath: /opt/hiero/block-node/logs
logSize: 8Gi
applicationStatePath: /mnt/archive-storage/block-node/application-state
applicationStateSize: 30Gi
pluginsPath: /mnt/fast-storage/block-node/plugins
pluginsSize: 5Gi

alloy:
monitorBlockNode: true
clusterName: "VALUE REDACTED"
prometheusRemotes:
- name: "hashgraph"
url: "VALUE REDACTED"
username: "VALUE REDACTED"
labelProfile: "ops"
lokiRemotes:
- name: "hashgraph"
url: "VALUE REDACTED"
username: "VALUE REDACTED"
labelProfile: "ops"
```

### Describe the expected behavior

When running `sudo solo-provisioner alloy cluster install --config=/etc/solo-provisioner/config.yaml` with a valid `alloy` configuration block and remotes, I expect the remotes to properly populate or if values are invalid, the tool should halt upon failed validation.

### To Reproduce

_No response_

### Additional Context

_No response_

Start at the `alloy cluster install` command and trace how `--config=/etc/solo-provisioner/config.yaml` is loaded, validated, and applied to the Alloy settings. Reproduce with the configuration shown, then confirm that the cluster name, block-node monitoring, Prometheus remotes, and Loki remotes are populated or that invalid values stop the command with validation errors.

Written by the indexing model from the issue text.