In TestEmbeddedCamundaOptimize the config is reset using the resetConfiguration method.

This uses `BeanUtils.copyProperties(defaultConfiguration, testOptimizeInstance.getConfigurationService())`, so non-primitives properties like lists,maps or custom classes are not reset during this process but given from one test run to another, causing side-effects based on test order.

AT:

• config reset uses deep clones of non-primitive properties to avoid side-effects