Add noConflict to Almond

[ghost]

At Atlassian we have a plugin which is used in all of our products which is responsible for the management and installation of other plugins. This central plugin must work with a variety of host products which have different front-end architectures, i.e. some which use almond and others which don't.

To ensure this central plugin works nicely with all products it's best if it provides its own dependencies (including almond) to ensure it:

• is not dependant on external products dependencies.
• maintains its own set of module definitions without potentially clobbering the host product's modules.
• works with multiple versions of the products irrespective of their front-end stack.

A way to do this is is to implement noConflict in Almond so the plugin mentioned above does not interfere with the product's copy (if it exists).

[ghost]

Closing until I've figured out the licensing / CLA requirements of this PR.

[jrburke]

Just getting through my support notification backlogs now:

I do not have plans to support this in almond itself, however, the goal of these kinds of small AMD API providers is that there would be multiple ones for different needs. So I encourage you to just keep your fork going on its own. If you feel like doing that, please add a link to it on this wiki page so that others might find it and use it if it fits their needs:

https://github.com/jrburke/requirejs/wiki/AMD-API-Shims