[Discuss] Remove eth1 backups from smartnode

[jshufro]

rocketpool service export-eth1-data was added to smartnode around the time besu and nethermind were, as a way to calm the nerves of a smartnode operator who wanted to switch execution clients.

The idea was that they could export a backup of the eth1clientdata volume to an external drive, switch clients, delete their local volume, and have the ability to import the backup should anything go wrong.

We've also included language in the guides about restoring from a backup in case of corruption.

Well-intending NOs have made it part of their regular maintenance to take backups, however...

1. Backups go stale quickly, and after some number of weeks, it becomes faster to sync from scratch that it is to restore a backup, since execution clients have snapshot syncing built-in (though it takes longer than eth2 for ethereumy reasons
2. They have trouble using the command and ask for support

I propose we remove the command- it's almost always a waste of time. Technical users who understand the drawbacks are capable of replacing the command with a simple .sh that stops eth1, copies the volume from the docker-root, and starts eth1 again.

Vote your opinion with emojis, or voice it in the comments below.