Companion for #1286 and #1287 - also updating follow-redirects version in package.json

Fixes #1286 - also updating follow-redirects version in package.json to ensure that maxBodyLength option is supported

Set maxBodyLength on follow-redirects to match maxContentLength on AxiosOptions

adding codetriage badge

Adding example of cancelling a POST request to readme

Removing unused dependencies

it seems when cancelling a post request we need to specify cancellation token as an axios parameter and not as a data item.

Fixing maxBodyLength exceeded error form follow-redirects when axios's maxContentLength is not exceeded

Adding redux-saga-requests to ecosystem in docs

Closes #1100.

Fix Markdown formatting for issue and pull request template

[skip ci]

Fixing type definitions so AxiosInstance can be invoked

Fixing interface of axios instance

Update buildURL.js

Update license date

Two if statements is unnecessary, we can replace with "if ... else ..."

PhantomJS is not used in axios.

Fixing typing issues #1154 #1147

Move window defined check before window.XMLHttpRequest check

Updating typings

security: upgrade follow-redirects

This would prevent tools like nsp to complain about a security issue from axios. It's something that got fixed in the package debug, and in order to benefit from that fix, it's necessary to upgrade to at least follow-redirects@1.2.5

The first argument in `axios.interceptors.response.use` is optional, in the case that you just want to intercept an error.

Ex:

```ts
axios.interceptors.response.use(undefined, error => {
...
});
```

refactor: !isArray(obj) is always true