(feature) Ability to follow a location header regardless of the http status option

~~**Describe the bug**~~
~~201 status with a location header does not redirect to location~~

~~**To Reproduce**~~
~~Steps to reproduce the behavior:~~
~~1. Create new post request to resource that returns a 201 status with a location header~~
~~2. Run request~~

~~**Expected behavior**~~
~~App to redirect to location header~~

**Desktop (please complete the following information):**
Version: Insomnia Core 2020.4.1
Release date: 9/22/2020
OS: Windows_NT x64 10.0.18362
Electron: 9.1.1
Node: 12.14.1
V8: 8.3.110.13-electron.0
Architecture: x64
node-libcurl: libcurl/7.69.1-DEV OpenSSL/1.1.1d zlib/1.2.11 WinIDN libssh2/1.9.0_DEV nghttp2/1.40.0

**Additional context**
Its common practice to have a REST API to return a 201 (Created) status with a location header (my use case) Ability to follow a location header regardless of the http status option would be useful

Start by reproducing the request described in the issue: a POST response with status 201 and a Location header, then inspect the HTTP redirect handling and the existing status option. Done means the client can follow the Location header for this response while preserving the existing behavior for other status options.

Written by the indexing model from the issue text.