Document minimum specs and configuration tuning

[achow101]

Currently the website does not contain any documentation with respect to minimum or recommended specs, or the configuration options that node operators can use to reduce memory and bandwidth usage. While these are included in the link to bitcoin.org's full node guide, some of the information there is outdated, and it's also not our website. We should have these docs on our website.

While we do have docs in the repo for reducing memory usage and traffic, I think these should also be on the website for better visibility (or at least linked to).

Credit to Kevin McSheehan for pointing out how there is no obvious guidance provided for nodes on low spec hardware.

[visualbasic6]

cool - thanks for the credit. i appreciate that.

but this is a consequence of my get header range oom that bsv paid $100k for, and yesterday's new release of an exploit wherein you just peer in multithreaded and ping faster than the remote machine can interpret. the headers issue appears rate limited now, though. well done to whoever did that remains unpatched for now - but will be sorted.

exploit code demo: https://asciinema.org/a/614446