Forest mint genesis

# Summary

Forest can't bootstrap a new network on its own - aside from some `lotus-seed` (not in the scope of this issue), it lacks Lotus's `lotus daemon --lotus-make-genesis=${LOTUS_DATA_DIR}/devgen.car --genesis-template=${LOTUS_DATA_DIR}/localnet.json --bootstrap=false`. This forces any devnet setup to start the network with Lotus as initializer, even though if later it's only Forest + Lotus-Miner that are driving the chain.

# Completion Criteria

- [ ] Implement missing flags. Note that it might not make sense to do them like Lotus does, inside the daemon. Perhaps a `forest-tool`/`forest-dev` utility would make more sense.

# Additional Links & Resources

Start by examining how Forest currently initializes a devnet and compare it with the referenced Lotus `daemon --lotus-make-genesis` command. Decide whether the functionality belongs in the daemon or a `forest-tool`/`forest-dev` utility, then verify that Forest can bootstrap a new network without Lotus as initializer.

Written by the indexing model from the issue text.