In certain scenarios having control over i18nManager#load mode is preferred, for example:
- in 1.1.10 version of forgerock-ui the default value is 'unspecific'
- in the latest version it is now 'current'
In either of these cases, how the localization files are structured are actually up for the end-users (since we currently only have english localization), and customers may wish to have different localization files for es and es-MX for example.
Allowing end-user control over the loadMode should also mean that they can optimize their deployments for the localization the way they want to implement them (using 'current' means that fr-CA will not fall back to fr if fr-CA is missing, 'unspecific' means that it's not possible to override es with es-MX).