Implement a custom HystrixPropertiesStrategy plugin

Add a custom HystrixPropertiesStrategy implementation where getCommandPropertiesCacheKey is overridden to return null so that HystrixPropertiesFactory will always generate a new HystrixCommandProperties for each new HystrixCommand instantiation.
My concern is that since there is actually _no way_ of unregistering anything and registering the same kind of plugin twice actually causes errors, having this in a trait would imply that it _can_ be reused somewhere else, when for all intents and purposes, this should be called only once during the application life-cycle: at it's start.

That's why I think it should belong in global : it is very much global (!), hooks into the application lifecycle, and shouldn't/can't be used anywhere else.