Syncing MaxScale ends up with different JSON configuration

Creating a monitor at runtime ends up producing an improper JSON object for the MaxScale that is synchronizing the configuration from the cluster. This happens as the JSON gets modified during the processing and the modified JSON gets saved as the final configuration instead of the original configuration that was found in the cluster.