Interop updates and refactoring

[austinabell]

Summary of changes
Changes introduced in this pull request:

• Interop updates and refactoring chain store logic to be more consistent
• Updated hello protocol handling to route requests through ChainSyncer
  • This isn't ideal in our current setup, because that thread could be busy syncing, but is fine for now
  • Could potentially access the heaviest tipset with some Arc shared memory between the libp2p thread and chainsyncer, which could be a better solution, but I won't make any big changes yet because we may want those messages being passed through the chainsyncer for metrics on the peers

Still a few things to be ironed out and debugged, but gives a much cleaner setup to work off of and split up remaining tasks.

#384 (Will try to detail issues to do now before closing that issue though)

Reference issue to close (if applicable)

Closes
Other information and links

[ec2]

Suggested change

	To run the node with custom config and bootnodes, the `--config` or `-c` flag can be used to specify a toml file with the options. The main configurations options include but are not limited to:
	To run the node with custom config and bootnodes, the `--config` or `-c` flag can be used to specify a TOML file with the options. The main configurations options include but are not limited to:

[dutterbutter]

LGTM just that one suggested change to the readme.

[dutterbutter]

imo the below is more clear. However, I will leave it to your judgment.

Configuration

Run the node with custom config and bootnodes

forest --config /path/to/your_config.toml

Example of config options available:

data_dir = "<directory for all chain and networking data>"
genesis_file = "<relative file path of genesis car file>"

[network]
listening_multiaddr = "<multiaddress>"
bootstrap_peers = ["<multiaddress>"]

Example of a multiaddress: "/ip4/54.186.82.90/tcp/1347"