Support a "Deploy to OpenWhisk" button

[krook]

As discussed with @csantanapr and @mrutkows we should create a shared service (perhaps even an OpenWhisk web action) that can deploy resources from an arbitrary GitHub OpenWhisk demo application repo that has a wskdeploy manifest file in it.

This should be modeled on the existing tool for deploying samples to Bluemix Cloud Foundry apps.

From the end user point of view (for example, someone who is looking to deploy their first sample app) they will see a button in the README (or other location, such a blog post) that says "Deploy to OpenWhisk." When clicked, the service will create all the resources the user needs to see what the application can do.

In addition, this service can also be used to automate TravisCI build testing for sample apps, to ensure they work with the latest OpenWhisk API.

A flow for this shared service might look like this:

1. User clicks the "Deploy to OpenWhisk" button
2. Link invokes an HTTP call to some endpoint along with sample app GitHub repo URL and the current logged in user context.
3. Service behind that HTTP call spins up a Docker container to clone the given repo, build the latest wskdeploy tool, and execute it with the repo's manifest file.
4. When done, the user should be redirected to the Bluemix console where they can see all of their actions.

This tool can start with the first 3 OpenWhisk 101 projects, but should easily be generic to be used for any repo with a manifest file.

• For a Data processing App from MessageHub changes there is a wskdeploy manifest available for a user to easily instantiate the PRODUCT IBM/ibm-cloud-functions-data-processing-message-hub#5
• For a Serverless API there is a wskdeploy manifest available for a user to easily instantiate the PRODUCT IBM/ibm-cloud-functions-serverless-apis#5
• For a Data processing App from Cloudant changes there is a wskdeploy manifest available for a user to easily instantiate the PRODUCT IBM/ibm-cloud-functions-data-processing-cloudant#5