Refactor Segment Name Generator

Currently there are three issues with `SegmentNameGenerator` classes -

* The implementations need to be supplied with exact arguments instead of general segment name generator config. e.g. You need to provide `dateTimeFormatSpec`, `pushType` , `excludeSequenceId` etc. but instead you can simply pass `segmentNameGeneratorConfig` to the constructor and let the implementation take care of extracting out props.

* Any change to segmentName logic requires changing the implementation classes. We can rely on something like templates to generate the segment name rather than having to implement code change.

* A lot of segment name generator props are duplicates in `BatchConfigProperties` as well. Addressing 1 should also help addresses this.

Start by locating the SegmentNameGenerator classes and BatchConfigProperties, then compare their constructor arguments and duplicated properties. Review how segmentNameGeneratorConfig is currently consumed and how segment-name logic is implemented. Done means implementations accept the general config, segment naming can be driven by templates, and duplicated properties are addressed.

Written by the indexing model from the issue text.