should we try to reuse the enums that really are the same for all? perhaps we do have CommonOptions at top level and add the Analytics enum there, but then extend that with CommonDistributedOptions (with its subclasses of ContainerOptions and AdminOptions) while having SingleNodeOptions extend directly from CommonOptions (the new CommonOptions, assuming the one that is included in this PR becomes CommonDistributedOptions)