[doc] Add a deployment checklist

[the-glu]

This PR follows #1469

It does add a deployment checklist, with the idea of listing each important steps for a production (or anything related, like a qualification, etc..) setup.

Checkbox are checkable and stored in the brower's stroage, providing (light) support of a real to-do list if needed.

It's partially redundant with some page (e.g. home, operations), but the idea is to centralize everything with pointers for non-local deployments.

[BenjaminPelletier]

Thanks, this looks good and I think is another valuable piece of documentation that will see a lot of interest in the very near future. In addition to a few comments below, I think we should change the term "Production". Multiple groups have the practice of deploying software to multiple environments, at a minimum including actual production serving end users and a shared qualification environment where software prereleases are qualified. The deployment into the qualification environment is fully relevant to all of this documentation, yet it is not production. Perhaps "Deployment checklist"? I know that isn't perfect because we also call running containers on a local machine a "local deployment". Nonetheless, I think I still lean toward "Deployment checklist" as accurate enough while being maximally obvious when it correctly applies. If there are concerns, possibly "Cloud deployment checklist" is more accurate as long as the USS isn't deploying on premises.

[BenjaminPelletier]

Pooling happens as part of following the per-infrastructure-choice deployment guide according to the "operations" pooling documentation -- for instance, steps 6 and 8 in the manual deployment documentation. It looks like the GCP and AWS deployment documentation are probably weak on making this point clear; I would expect them to say something like steps 6 and 8 in the manual documentation. The important thing for this PR though is that I don't think "pool your DSS instance" is a separate step from "Deploy the DSS instance".

[the-glu]

Yes the documentation is not clear on that.

For me there are two points (or subpoints): you deploy it, by spawning services and, optionally, you configure it correctly in a pool. First step you can probably do it alone and it may work directly in the non-pooled case, second step involve "special work" that need other DSS participants.

I also think that pointing to the pooling part is important, as it's a 'core' operation (plus others part are not clear (yet)).

I moved it to a sub-step in this document + tweaked wording, would that work?

[the-glu]

@BenjaminPelletier Ready for a second pass of review, I reworded "Production" to "Deployment checklist" in general + added a menu entry as well