Auto deploy workflow-manager-api to production on merges to master

[arschles]

This issue is for setting up auto deployment to production. It's intended for the following:

• Force our tests and automation to get good enough to ensure the stability needed to do auto-deploys
• Set up auto-deployment in travis (I believe it already auto-deploys to staging)

[jackfrancis]

@arschles @slack @sgoings

This is the solution we have in place at present:

• merges to master automatically deploy to staging (as per travis)
• new release tags (currently all tags, but by convention we only tag a commit during a "release") will trigger a Jenkins build to production

We should consider the above "experimental" in terms of process, especially the federated responsibility among Jenkins and travis. This experimental phase will give us some real-world experience (pros/cons) with both Jenkins and travis, during which we can tease out the various CI options of both platforms; and at the conclusion of which we'll have the expertise to build a permanent CD-type workflow (using only Jenkins or only travis) for the API. At that point we'll create a follow up issue w/ details on implementation objectives.

We'll favor Jenkins over travis, which is the company-wide idiom at this point (unless we determine that travis more effectively does what we want).