Accept an array as localesPath in useLocaleRequired, withLocaleRequired, and LocaleRequired

[eliebman-godaddy]

Summary

Support passing an array of localePaths to useLocaleRequired, withLocaleRequired, and LocaleRequired
This helps optimize load times by fetching paths in parallel. Previously, consumers had to nest withLocaleRequired HOCs in order to ensure fetching of multiple paths, which caused requests to run in series, creating longer page load times.

Addresses Issue #776

Changelog

• Accept an array as localesPath in useLocaleRequired, withLocaleRequired, and LocaleRequired

Test Plan

Unit Tests are passing
Have not been able to verify inside an application due to node versioning issues, but we should probably verify this functionality with npm link before merging.

[jpage-godaddy]

If you're interested, there's a MaybeMultiple (or perhaps it was called MaybeArray) type that you can import and use.

[jpage-godaddy]

You'll also need to update the server-side code for withLocaleRequired so it includes all of the strings in the server payload; currently it expects just a single thunk or string. You've only covered the client-side loading.

[eliebman-godaddy]

You'll also need to update the server-side code for withLocaleRequired so it includes all of the strings in the server payload; currently it expects just a single thunk or string. You've only covered the client-side loading.

@jpage-godaddy, It seems like serverside, in getInitialProps, we just pass localePathPart directly to serverLoadData, which looks like it already supports arrays

Is there some other server-side code I'm missing?