feat: add isAggregator flag to validator configuration

[ch4r10t33r]

Summary

Add support for configuring nodes as aggregators through validator-config.yaml. This allows selective designation of nodes to perform aggregation duties by setting isAggregator: true in the validator configuration.

Changes

• Add isAggregator field (default: false) to all validators in both local and ansible configs
• Update parse-vc.sh to extract and export isAggregator flag
• Modify all client command scripts (zeam, ream, qlean, lighthouse, lantern, grandine, ethlambda) to pass --is-aggregator flag when enabled
• Add isAggregator status to node information output in parse-vc.sh

Usage

To designate a node as an aggregator, simply set isAggregator: true in the validator-config.yaml:

validators:
  - name: "zeam_0"
    privkey: "..."
    enrFields:
      ip: "..."
      quic: 9001
    metricsPort: 9095
    isAggregator: true  # This node will be an aggregator
    count: 1

The spin-node.sh script will automatically detect this configuration and pass the --is-aggregator flag to the client.

Test plan

• Verify that nodes with isAggregator: false start without the --is-aggregator flag
• Verify that nodes with isAggregator: true receive the --is-aggregator flag
• Test with both local and ansible deployment modes
• Confirm backward compatibility (nodes without the field default to false)