Boost dependencies

At the moment we have a simple release strategy: we just merge things into main and cut a release whenever we're ready.

If we want to depend on lotus `master` I think we'd need to create release branches corresponding to lotus release branches. So we'd need to weigh up the cost/benefit of that maintaining those branches.

The reasons boost depends on lotus are:
- boost uses several libraries and utilities from lotus (eg reading config files)
Long term these should probably live in a separate package
- boost depends on go-fil-markets, and some of the things that go-fil-markets needs live in the lotus repo (eg Batching Publish deals)
Medium term these should probably move into the boost repo (once go-fil-markets is deprecated).
- boost calls the lotus RPC API.
I'm not sure of the details of how go.mod works but it may be possible to depend on the lotus RPC client library without bringing in all the other libraries in lotus. Otherwise maybe the lotus RPC client should live in a separate package.