This one has a couple of problems that I want to discuss with you guys.
The whole point of `Liferay.provide` is to provide a global function (which could be called at any time) that may have asynchronously loading dependencies.
However, there are some problems here:
1. There is no dependencies being passed to `provide`, which means that there's no advantage to doing this or just doing `WIN[instance.ns('postProcessTranslation')] = A.bind('_postProcessTranslation', instance);`.
2. The reason we use `provide` is for functions that may be called at any time before the dependencies are loaded. However, this function's dependencies are already loaded when we're defining it, however, the function, if called before this module is loaded (and an instance of the component instantiated), it will error out, which just overall defeats the purpose of `Liferay.provide`.

So I see some issues that we need to find a way to address.
1. We have a function that we want to define globally, and can be called at any point.
2. This function has a dependency, not just on this module, but on a specific instance of this module.

Maybe in this specific case, we can guarantee that update_translation_redirect.jsp will never attempt to call `postProcessTranslation`, but since we're defining a new pattern, I would like to make sure we cover our bases.

The only alternative I can think of would be to switch this all over from being a provided method, to being an event based system, where update_translation_redirect.jsp fires a global, but namespaced, event, and in `_bindUI`, we subscribe to it and handle it that way.

What do you guys think? I'm open to other ideas as well.