S3 overrides as option

[mrmarcsmith]

This is the second attempt with cleaned up code. see #40 for the old PR

Background: when using parse server with a config file there is no way to specify S3Override options.
-This change doesn't affect the current method of passing s3overrides = backwards compatible.
-s3overrides would now be accessible by via parse-server config file like this:

"filesAdapter": {
    "module":"parse-server-s3-adapter",
    "options":{
        "s3overrides": { 
            "endpoint": {
                "protocol":"https:",
                "host":"$FILEURL",
                "port":443,
                "hostname":"",
                "pathname":"/",
                "path":"/",
                "href":"https:///"
            },
            "s3BucketEndpoint": false,
            ANY OTHER S3OVERRIDES GO HERE... 
        },
        "baseUrl": "https://",
        "directAccess": true,
        "accessKey": "",
        "secretKey": "",
        "bucket": "",
        "region": ""
    }
}

[codecov]

Codecov Report

Merging #50 into master will decrease coverage by 23.28%.
The diff coverage is 88.88%.

@@             Coverage Diff             @@
##           master      #50       +/-   ##
===========================================
- Coverage   94.11%   70.83%   -23.29%     
===========================================
  Files           2        2               
  Lines         136      144        +8     
  Branches       27       31        +4     
===========================================
- Hits          128      102       -26     
- Misses          8       42       +34

Impacted Files	Coverage Δ
lib/optionsFromArguments.js	95.52% <88.88%> (-1.09%)	⬇️
index.js	49.35% <0%> (-42.86%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 147e506...dc099b2. Read the comment docs.

[mrmarcsmith]

Hi Friends! Any update on this?

just going to fix the nits

[acinader]

@mrmarcsmith I just pushed 1.2.0 to npm with this change. thanks for the contribution!