This is to make it easier to send these configurations across the network in a running Apache Beam pipeline.
The API of Beam asks for any metadata driving all transforms and functions to be Serializable. Reading from and writing to Neo4j is no exception to this. This requirement in turn forces us to mirror all methods of Config, SessionConfig and TransactionConfig in new Serializable classes and write new Builders for this as well.