Document our config setting and modules deployment in function of the host ressources

[ariard]

As we have more features and config settings, some targeted for high-performance hosts, while others definitely designed for low-performance hosts, ideally we should have user documentation (in the repo or on the website) guiding the users to select the best options and batteries deployment (e.g relying on lightning-rapid-gossip-sync) in function of host resources.

As a conversation input : #1625 (comment)

(Otherwise, I'm worried we end up like in the Linux space, where subsystems and features are well-documented by their authors though there is no unified point of information on all the factors affecting the common disk/memory/cpu time ressurces)

[moneyball]

We have deprecated use of the term "batteries." It is "modules."

[ariard]

With that regards, in the future if we enable the shipment of confidentiality improve at the cost of more disk : https://github.com/TonyGiorgio/p2wsh-utxo