optimize gossamer archive node size

## Task summary

- currently the gossamer kusama archive node disk size is larger than expected, at 1.3mil blocks the size of the DB is 34GB, but the size of a substrate kusama archive node at 1.6mil blocks is 15-20GB
- optimize this to be the same size or less than substrate
- potential solution is adding compression to the database layer, currently there is no compression

`opts.Compression = options.Snappy`

Also, we should update chaindb to allow for badger options to be passed from gossamer (via a config)