Show keys of Blox SSV operator node service

[stefa2k]

@daGscheid please define in this issue how to show the secret & public key of the operator node. Also define how to link to the node operator page of https://app.prater.ssv.network/

[daGscheid]

I thought I would write down all my thoughts about the frontend registration process here.
The flow of registration after having installed the SSV Network Component should look in my mind something like this:

After having installed the SSV component on the top bar the SSV symbol appears. This is how you would generally interact with the SSV service.
(Important to consider: What if the users doesn't have all the necessary components to run a SSV operator node? - prompt listing missing components?)

Pressing the button they are 2 cases we have to differ:

1. first time registering users
2. a migrating operator seeding their public operator key with their private/secret key
   While not to consider for the testing versions, I would like to have some idea how we handle the 2nd case in the backend to know where to put it best in the frontend @stefa2k. Currently I am thinking about either during the setup process as installation option so you could seed the public operator key or simply via a selection with the differentiation - Register (generating Key) / Sign In (Seeding Key) - before going to the registration page.

Considering future services both cases will most likely be present in some form, and a uniformed probably not out of reach.
Should come back to that thought when we tackle the second integration.

Considering purely the 1st case, the button leads the user to the SSV Operator Registration Page. There is an interesting questions in how to abstract the registration process. Given that it prompts a transactions. For testing a link to opening up ssv's operator page in the standard browser might be enough. I wouldn't recommend this as a lasting solution for usability reasons however - the user should be force to leave his cave as few times as possible.
Here would be a suggestion for what this could like inside of Stereum:

On the Operator Page you are asked to pick a Operator Name & put in your Ethereum Address.
A small warning with a checkbox orders you to copy your operator private key. Pressing the copy button next to the operator private key, checks the checkbox and allows the user to proceed.

Pressing "Register "prompts a transactions, writing the information into a smart contract. This will probably change over time, we will see what their V2 will look like.

After registration you will land here:

Pressing the SSV Button will open the same page.

The outlined commands by order are:
Website - link to project website, opened in standard browser
Github - link to SSV github, opened in standard browser
Discord - SSV Discord Invite, opened in standard browser

Copy Operator Key - Copies Public Operator Key
Operator Page - Opens your SSV Operator Page in the standard browser. The SSV Explorer Oage follows a logic that either takes the Ethereum address or the public operator key (no exact insight) to generate a weblink.
Grafana Dashboard - SSV features their own Grafana Dashboard which you are able to navigate to here directly

The validator keys themselves will be displayed in Stereum on the Staking Tab, but this should be discussed in another issue.

[stefa2k]

Thanks @daGscheid for the explanation, for this issue it's only relevant how to show the keys (as you lined out in your UI drafts) and where the registration button goes. Let's finish this first with this issue and think later about how to solve the registration through Stereum UI.