Build plugin files into /dist for use w/o package manager

[benvinegar]

Continuation of @floriangosse's work in #455 (addressing issue #446)

Added here:

• Each plugin is exported onto the Raven global as Raven.PluginnamePlugin, e.g. Raven.AngularPlugin,Raven.ConsolePlugin, etc
• Unlike CDN "combo builds", these individual plugin files do not auto-add themselves to the Raven ecosystem; they have to be added manually via Raven.addPlugin

Example usage:

<script src="node_modules/dist/raven.js"></script>
<script src="node_modules/dist/plugins/angular.js"></script>
<script src="node_modules/dist/plugins/console.js"></script>
<script>
Raven
    .config('https://[email protected]/1')
    .addPlugin(Raven.AngularPlugin)
    .addPlugin(Raven.ConsolePlugin)
    .install();
</script>

[Sija]

Wouldn't be nicer to have 'em (plugins) in separate namespace, like Raven.Plugins? You could inspect just this namespace to find out which plugins are loaded at the given moment.

[benvinegar]

@Sija – That's a good idea. I'll make that change, barring any objections from comments here.

[benvinegar]

cc @mattrobenolt

[benvinegar]

Okay, going to merge this in for a 2.1.0-beta release today. If we hit any snags we can follow up w/ fixes before 2.1.0 goes out officially.

[luiscvalmeida]

@benvinegar please fix your comment, where you specify: addPlugin(Raven.AngularPlugin), it is now addPlugin(Raven.Plugins.Angular), same to the console plugin.