t-ECDSA client & ETH bonding/staking documentation

[creckhow-zz]

https://github.com/keep-network/keep-core/pull/1310#issuecomment-604674096 Pulling this out of the Keep-Core docs and filing an issue here on ETH staker documentation. Requirements below:

1.) @sthompson22 in or before or after your section about logging, I want to see a brief description of the different calls a client/staker could receive, like:

• Call to participate in a t-ECDSA signer set for tBTC
• Call to tBTC redemption
• Call for malicious actor liquidation (tBTC)

And of course what the technical bit would be, I'm assuming it's something they're looking for in the logging?

2.) @sthompson22 I know this hasn't been written/developed yet, but we're going to need a section about bonding ETH. Things such as:

• minimum stake
• any differences in signer selection based on ETH stake
• what happens to bonded ETH that isn't working in a signer set

Some of these items may be more for @Shadowfiend

3.) @sthompson22 @Shadowfiend ETH bonding liquidations. We're going to need description of how this works, including courtesy calls. Need to see:

• what the parameters are (ie. price drop threshold, risk of slashing, peers submitting challanges)
• what happens at a courtesy call
• what they need to watch for (in the logs? on the blockchain?) to know a courtesy call happened or liquidation is coming
• point to maintainer scripts that can help with this^

4.) @sthompson22 @Shadowfiend I'm not sure if this goes best near the logging section or earlier on, but there needs to be explanation of availability requirements and how to watch for them/manage them.

5.) @sthompson22 @Shadowfiend same thing for slashing vectors -- what they are, how to monitor and manage for them.

6.) All the setup stuff, configuration, docker, deployment, etc. .. the tech stuff, I'm sure much of it's c/p from the random beacon docs

[creckhow-zz]

Also stuff on minimum KEEP stake