beacon_metrics_gazer & light_beaconchain_launcher don't account for the validator_count

[h4ck3rk3y]

this leads to misleading data being reported on the light beacon chain explorer

sample input

{
	"participants": [
		{
			"el_client_type": "nethermind",
			"el_client_image": "nethermind/nethermind:latest",
			"el_client_log_level": "",
			"cl_client_type": "lighthouse",
			"cl_client_log_level": "",
			"cl_client_image": "sigp/lighthouse",
			"el_extra_params": [
				"--Mining.ExtraData=\"Discovery Node\""
			],
            "validator_count": 0
		},
		{
			"el_client_type": "nethermind",
			"el_client_image": "nethermind/nethermind:latest",
			"el_client_log_level": "",
			"cl_client_type": "lighthouse",
			"cl_client_log_level": "",
			"cl_client_image": "sigp/lighthouse",
			"el_extra_params": [
				"--Network.MaxActivePeers=0",
				"--TxPool.Size=0",
				"--Mining.ExtraData=\"Proper Validator Node\""
			]
		}
	],
	"network_params": {
		"capella_fork_epoch": 1,
		"seconds_per_slot": 5
	}
}

validators should have been reported against cl-2 but they are incorrectly reported against cl-1 as the logic doesn't account for the validator_count change