Bundler-friendly entry point (#88)

* Use the browser entry point instead of a webpack build for `browser` in `package.json` (see [the intended use of the browser package.json field](https://github.com/defunctzombie/package-browser-field-spec) for justification).
* Loosen lodash & uuid version requirements to increase potential for package reuse by bundlers

Author: mikeproeng37

packages/optimizely-sdk/package.json

@@ -3,7 +3,7 @@
   "version": "2.0.0",
   "description": "JavaScript SDK package for Optimizely X Full Stack",
   "main": "dist/optimizely.node.js",
-  "browser": "dist/optimizely.browser.cjs.js",
+  "browser": "lib/index.browser.js",
   "scripts": {
     "test": "mocha ./lib/*.tests.js ./lib/**/*.tests.js ./lib/**/**/*tests.js --recursive",
     "test-travis": "npm run test && grunt",
@@ -33,11 +33,11 @@
   "homepage": "https://github.com/optimizely/javascript-sdk#readme",
   "dependencies": {
     "json-schema": "^0.2.3",
-    "lodash": "^4.13.1",
+    "lodash": "^4.0.0",
     "murmurhash": "0.0.2",
     "request": "~2.83.0",
     "sprintf": "^0.1.5",
-    "uuid": "~3.0.1"
+    "uuid": "^3.0.1"
   },
   "devDependencies": {
     "bluebird": "^3.4.6",