chore(package): use more appropriate deps ranges

Note on deps starting with 0.x.y:

Hat matching may be considered broken because it
wont update ^0.1.2 to 0.2.0. When the software is emerging
use 0.x.y versions and hat matching will only match
the last varying digit (y). This is done on purpose.
The reason is that while the software is evolving
the API changes rapidly.

Author: char0n

.npmrc

@@ -1,2 +1 @@
-save-prefix="="
 audit-whitelist=[]

package.json

@@ -105,19 +105,19 @@
     "xmock": "=0.3.0"
   },
   "dependencies": {
-    "@babel/runtime-corejs2": "=7.10.4",
-    "btoa": "=1.2.1",
-    "buffer": "=5.6.0",
-    "cookie": "=0.4.1",
-    "cross-fetch": "=3.0.5",
-    "deep-extend": "=0.6.0",
-    "fast-json-patch": "=2.2.1",
-    "isomorphic-form-data": "=2.0.0",
-    "js-yaml": "=3.14.0",
-    "lodash": "=4.17.19",
-    "qs": "=6.9.4",
-    "querystring-browser": "=1.0.4",
-    "traverse": "=0.6.6",
-    "url": "=0.11.0"
+    "@babel/runtime-corejs2": "^7.10.4",
+    "btoa": "^1.2.1",
+    "buffer": "^5.6.0",
+    "cookie": "~0.4.1",
+    "cross-fetch": "^3.0.5",
+    "deep-extend": "~0.6.0",
+    "fast-json-patch": "^2.2.1",
+    "isomorphic-form-data": "~2.0.0",
+    "js-yaml": "^3.14.0",
+    "lodash": "^4.17.19",
+    "qs": "^6.9.4",
+    "querystring-browser": "^1.0.4",
+    "traverse": "~0.6.6",
+    "url": "~0.11.0"
   }
 }