Add good nodes.json file to github, and include into quickstart script and install docs

[fileflume]

Some nodes - for unknown reasons - struggle to connect to peers. This is seen when:

1. When starting a node, the node does not connect to any peers, and doesn't start to sync the database immediately.
2. Connects to 1-4 peers, but fails to maintain them (often dropping and regaining them), or doesn't gain any more over time.

The reasons for this are unknown.

A solution to this is to delete the nodes.json file ( found here: ./fusenet/database/FuseNetwork/network/nodes.json) and replace it with a known good one from a node with many peers.

To stop this issue happening, it would be beneficial to include a 'good' nodes.json file in the initial node set up script (quickstart.sh)

Actions:

1. Maintain a good nodes.json file in this repo.
2. Include the download and install of nodes.json in the quickstart script (either manually or automatically)
3. Update the documentation to reflect this change, and point users who experience this issue to this solution.

[Andrew-Pohl]

Similar in part to #82. Think we need to be careful copying nodes files since they are actually node specific (not sure if there is some edge cause with attempting to connect with yourself). I have a suspicion that the peer issue is due to the nodes.json file being full of old nodes which are no longer present.

The issue at start up was due to incorrect enodes for the bootnodes. This has been resolved recently :)

@fileflume you ok for me to close this and we continue on #82 ?