Use browserify._options.paths when doing dependency resolution for composes

[ryngonzalez]

Where webpack and css-loader play well together when doing custom module resolution with resolve.moduleDirectories or resolve.alias, css-modulesify does not currently take into account browserify._options.paths when doing module resolution for composes statements.

css-modulesify should pass along the paths option from Browserify to css-modules-loader-core to correctly resolve composes statements like 'shared/styles/colors' — which currently throws an error like this:

{ [Error: ENOENT, open '/Users/ryan/Projects/myApp/browser/app/components/myComponent/shared/styles/colors.css']
  errno: -2,
  code: 'ENOENT',
 path:'/Users/ryan/Projects/myApp/browser/app/components/myComponent/shared/styles/colors.css'}

[juliankrispel]

@ryngonzalez this isn't actually fixed right?