Builder pattern for configs

[Shourya742]

Currently, our configs for both the taker and maker are quite verbose. We don’t want all the config fields to be accessible by third parties; only a specific set of fields should be available. Since the new method for initializing these structs is quite lengthy, we plan to use the builder design pattern. This will make it easier for third parties to modify the configurations with minimal effort. Change the config for both, to follow this.

[DaCatBeam]

@Shourya742 Are you looking to retain the default behavior of writing config files for the Maker and Taker Builders on non-existence of the config files?

[Shourya742]

@DaCatBeam We gonna still retain the default behaviour, but gonna make the initialization a bit more convenient.