Integrate *Activation* process into scheduled runs.

[mathomas]

Possible Options (we're leaning strongly toward the first):

• Have activation just run as another step in the main index.js of the existing Lambda , along with introduction (same function, more functionality)
  • pro: simplest approach, easy code reuse (just refactor existing code to fit)
  • con:
    • must always process both introduction and activation at same time
    • can't be scheduled separately, as currently written/conceived, failure of introduction will cause activation not to happen (probably not a huge problem)
    • possibility of Lambda timeout (but doubtful?).
• Use URL parameter/path to separate the functionality, but on the same endpoint
  • pro:
    • introduction/activation can be scheduled separately and have different result objects
    • easy code reuse
  • con: if/else to split functionality in index.js-- lack of cohesion
• Brand-new function endpoint/module in same project
  • pro: separation of concerns
  • con: difficulty of code reuse
• Separate project
  • pro: separation of concerns
  • con: complexity:
    • separate CodeStar projects
    • separate Github repos
    • difficulty of code reuse