Implement route /validatorsPerformance route in frontend. The new route will be available from the toolbar. The way it will work is:
When clicking on the button to redirect to the /validatorsPerformance route, the URL will be built with all the validator indexes/pubkeys as query parameters of the URL, so the performance UI will be shown for all the validators loaded in the brain
Furthermore, when the user clicks on the existing icon for beaconcha.in with a preset of validators selected there will be shown a pop-up where the user will be able to choose between: "Local validators performance" vs "Remote validators performance - beaconcha.in". In both scenarios the URL will be built with the validators indexes/pubkeys selected as query parameters.
Implement route
/validatorsPerformanceroute in frontend. The new route will be available from the toolbar. The way it will work is:/validatorsPerformanceroute, the URL will be built with all the validator indexes/pubkeys as query parameters of the URL, so the performance UI will be shown for all the validators loaded in the brain