Adds test case for silverstripe/silverstripe-translatable#97
Even though it is an edge-case, some sites may allow translation groups to be composed of different classes. In that case, Translatable->getTranslations() should still work. Also, this commit adds a helper function for testing two array for equality where you don't care about the order of the elements. This cleaned up a lot of copy and paste boilerplate code that was sorting arrays to test.
If the locale-filter was disabled before calling the method, it would be enabled after calling getTranslations, this commit now only re-enabled the locale-filter if it was enabled before calling the method...
This builds on 44f8180, but reverts most of it. The changeset had a logical flaw where it stored state on the Translatable extension where it was specific to a FieldList. This meant side effects when getCMSFields() was called more than once, such as in the CMSSettingsController template. Note: We shouldn't need to call getCMSFields() more than once because its an expensive call, but that's a missing feature in the template caching layer rather than a problem with the Translatable extension.
… been created.
…te translations of dependent objects