Add update_ecs job to Circle build, based on TACO and rialto-derivatives

[atz]

Here's a build that completed and apparently updated the actual ECS container:
https://circleci.com/gh/LD4P/sinopia_profile_editor/530?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

Note, because this job has nothing to do with the code (which is separately posted to docker hub) and only concerns itself with AWS commands, it uses an entirely different docker base image so that Python (and jq among other tools) is already installed!

You can review that CI output for effect. I then added the workflow relationship so that deployment only happens after successful register_image (i.e. only after merged to master).

[coveralls]

Pull Request Test Coverage Report for Build 543

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 5 unchanged lines in 1 file lost coverage.
• Overall coverage remained the same at 0.0%

---

Files with Coverage Reduction	New Missed Lines	%
source/assets/js/modules/profile/directives/export.directive.js	5	0.0%

Totals
Change from base Build 428:	0.0%
Covered Lines:	0
Relevant Lines:	1173

---

💛 - Coveralls

[jermnelson]

Looks good to me; I'll be interested to see a successful run the next time master is merged. I think @SaravShah would be the better reviewer to merge this branch.

[ndushay]

I'm not looking at this closely right now, but ... what do you think of only dealing with the production npm install stuff if the tests pass and/or if we're in master branch? Just thought of it while waiting for an unrelated build to pass CI.

[atz]

@ndushay It is a subset of of the npm install for CI. So doing it accomplishes part of the larger install and should be done first, in the same "job".

Secondly, the dependencies themselves are being cached, so it is very fast: 4 seconds.