[TIMOB-9662] Android: Nested CommonJS Modules Replace Existing CommonJS Modules

Problem

When nesting CommonJS modules, module definitions can override existing CommonJS module definitions. This is a regression introduced sometime in the last month, though I do not have a specific point.

Reproduction

Attached "NestedConfusionReproduction.zip". Extract it to the Resources directory of an app, and run it on any Android environment. (Note that in this reduced reproduction, moving some of the requires around can avoid this bug. But in larger projects, or more complicated require scenarios, it cannot be so easily avoided.)

What's Happening Wrong in Reproduction

The app does the following: - app.js require's a specific view (ti.cloud.ui/buttons/chooseAPhoto). - The specific view requires a generic view (ti.cloud.ui/buttons/generic). - Both views require a single utility module (ti.cloud.ui/utils) and store it in a variable U. When the generic view's createView method is called, it alerts the U variable. It also alerts a fresh require of the utility module. The expected behavior is these two would output the same thing, right? But the alert shows that both are messed up: U contains buttons/generic and the fresh require contains buttons/chooseAPhoto. (Each has unique methods, so it is easy to tell which module has been passed to alert.)