Testnet securely maintain a pool of recovery codes

[CMCDragonkai]

Once we have the ability to use PK_RECOVERY_CODE to automatically bootstrap the PK keynodes, we need to create at least 1 recovery code and 1 root key to be used.

The recovery code must be kept secret. I'll maintain this right now. The root key will be inside AWS's block device mounted into the ECS container and this will be kept safe inside AWS.

The recovery code will need to be used as an environment variable for ECS for the testnet.

Eventually we can store the recovery code inside a running Polykey node, and make use of AWS integrations, like our wiki page: "Service Deployment Secrets with AWS ECS".

Doing this should ensure that we don't need to maintain the volume state mounted in to the ECS container, it just has to be mutable, but it can be deleted, since everything can be recovered.

Tasks

1. - Use pk bootstrap locally to generate a recovery code and root key.
2. - Save the recovery code securely.
3. - Try using pk bootstrap on a different directory and see if the same root key is used. Compare them.
4. - Delete the root key.
5. - Use the recovery code for ECS Task Definition

This will be done for 1 single testnet node. We can scale this up later.

[joshuakarp]

Start date changed from Nov 11th to Nov 17th (based on delays in #231).

[joshuakarp]

Start date changed from Wednesday Nov 17th to Friday Nov 19th (delays in #269, #231, and CLI MR on Gitlab).

[joshuakarp]

Start date changed from Friday Nov 19th to Wednesday Dec 1 (delayed from refactoring work in #283).

[CMCDragonkai]

Going to bootstrap this from a password manager.