Using a log4j appender as a custom-handler should invoke the activateOptions if required

Currently the OptionHandler.activateOptions is only invoked during construction of a log4j appender. This invocation should happen if any property is updated or added. The invocation of this method should also only happen once. Multiple invocation could result in errors or leave the appender in an invalid state.