ConfigurationRule sets global configuration for the duration of a test, making sure to reset the configuration afterwards. This approach is preferred over manually calling Configuration.set in
test setup and ConfigurationTestUtils.resetConfiguration in an @After method. With the rule we manage configuration in a single place and don't need to worry about forgetting to reset it.
Currently, there are still many places in our tests where we call Configuration.set directly when we could use ConfigurationRule instead. The goal of this ticket is to change these tests to use ConfigurationRule