Plumb config

[rohancme]

This PR is a continuation of #453

It should resolve #190, #284 and to some extent #261. I've plumbed timeouts through wherever implemented.

Files that are deleted in this PR are due to changes being made in #511 and #513 (Removing pop from storage and removing olympus as a storage implementation), so ideally this should be merged only after those changes have been approved and merged.

[codecov-io]

Codecov Report

Merging #517 into master will increase coverage by 3.83%.
The diff coverage is 56.94%.

@@            Coverage Diff             @@
##           master     #517      +/-   ##
==========================================
+ Coverage    41.2%   45.03%   +3.83%     
==========================================
  Files          99       97       -2     
  Lines        2830     2782      -48     
==========================================
+ Hits         1166     1253      +87     
+ Misses       1554     1409     -145     
- Partials      110      120      +10

Impacted Files	Coverage Δ
pkg/config/cdn.go	0% <0%> (ø)
cmd/olympus/actions/merge_db.go	0% <0%> (ø)	⬆️
pkg/config/timeout.go	0% <0%> (ø)
pkg/storage/gcp/deleter.go	62.5% <100%> (ø)	⬆️
pkg/storage/module/upload.go	97.22% <100%> (ø)	⬆️
pkg/download/goget/goget.go	66.31% <100%> (-0.36%)	⬇️
pkg/storage/gcp/saver.go	62.5% <100%> (ø)	⬆️
pkg/storage/module/delete.go	97.22% <100%> (ø)	⬆️
cmd/proxy/actions/filter.go	75.75% <100%> (ø)	⬆️
cmd/proxy/actions/app_proxy.go	76.92% <100%> (ø)	⬆️
... and 27 more

---

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 70167dc...013d525. Read the comment docs.

[rohancme]

Also resolving conflicts in this PR is going to be SUPER annoying :) I'll probably do a squash and rebase after reviews

[ghost]

Might i suggest a squash and rebase first? That way we can start clean now that the config file PR is done.

[michalpristas]

i'm also leaning towards rebase-review order. In case of rebase just ping us directly and we can put priority into reviewing this and not pushing anything else in

[rohancme]

Working on this today. I'll attempt a squash + rebase but there are so many conflicts I might just start afresh.

[rohancme]

@robjloranger @michalpristas closing this in favor of #627 . There were simply too many merge conflicts.

This also forced me to get caught up with the latest changes :)