Also fixes bad redirect in build script.

* API GW V2 CLI - Add 'wsk api' command
- Support both 'wsk api-experimental' and 'wsk api' commands (separate PR wil deprecate `api-experimental`)
- 'wsk api' command requires that the target action exist and that it's a web action

* API GW V2 CLI - 'wsk api' tests
* Add "COMING SOON" label to 'wsk api' help
* API update needs additional param
* Reduce travis test execution time

Also, change working directory for Python actions to allow relative path access to file system.

Re-enable build swift/python containers (for tests to run).
Add unicode unit test for swift action container.
Allow for reinit with swift for use with invoke.py.
Fix unicode regression for swift actions.
Refactor unicode tests to add coverage - now also for base action container.
Set string encoding to utf-8 for swift action proxy.
Rewrite result extraction to avoid splitting and printing logs one line at a time.
Skip decoding when process output is a string; already utf-8.

Consolidate base64 encoding in CLI; remove Jar field in exec.

Update tests to work in both Python 2 and Python 3.
Rename pythonaction to python3action for container image name for clarity.
Add tests for python:2 and python:3.
Add image names for all the actions. Rename javaaction to java8action for consistency.

* Decode subprocess output bytes to text in actionproxy.

* Update swift3runner build step to capture stdout/stderr,
and decode if necessary.

Remove license headers from just test/dat path

Remove subtypes.

Move exec utils for image construction to singleton.

Rebase

# This is the 1st commit message:
Update header to comply with Apache requirements

Additionally, provide proper header (with script description) using PEP8 compliant string literal.

# The commit message #2 will be skipped:

#	Update box-upload.py

# The commit message #3 will be skipped:

#	Update invoke.py

# The commit message #4 will be skipped:

#	Update actionproxy.py

- Remove unused dependencies
- Define dependencies as compile time to be able to include them from other projects
- Standardize layout

* Bumping restassured version

* Update gitignore to include .cache-tests

Add manifest schema.
Add utilities to read Exec runtimes from manifest.
Add runtimes manifest to ansible group vars.
Write out manifest to whisk.properties and make available through WhiskConfig.

The change in #1946 introduced a regression such that it did not allow for Node.js zipped actions which contain an index.js but not a package.json. This is a valid configuration and should be supported.

Using the Windows Explorer method of creating zip actions results in an incorrect zip structure. OW requires that package.json be found at the root of the zip, while the Explorer action insists on putting everything inside a top-level folder inside the zip.

Return an explicit error when package.json is not found at the root of a zipped action.

* Normalize initializer for all execs.

* Handle empty code for blackbox.

* Do not include code if null.

Refactoring of init method into an init-from-source and init-from-zip.
Support a zip file containing more than one python file.
The zip file must contain a file called __main__.py that defines a "main" method.

Log an error when python zip does not include required file.

This removes lots of code related to a deprecated 1:n mapping of keys to namespaces. The /namespaces call will now only yield exactly one namespace, which is the namespace of the key you're providing.

test case fix when running on windows/vagrant

Remove Externalized Strings that do not Belong

Remove rotted script.

Adds bit to Exec to indicate action my not longer be activated or updated.
Adds checks for unsupported runtime in Actions API and report proper error.

Drop Swift 2 support
Adds tests.

The invokers ping the controller through a seperate topic in Kafka to indicate they are still alive. This is groundwork for a more sophisticated health protocol for our invokers.

* Remove unused script name variable for node js actions.

* Allow zip action without checking the kind - let backend determine if supported or not.

* Flatten exec hierarchy to remove unnecessary distinctions.

It should be assumed that /run only happens after /init which should itself ensure that the container is running and ready. With that in mind, it does not make sense to attempt to retry posting to the /run endpoint on connection failures. Such a failure is an indication that something catastrophic has happened to the container, and no attempt at recovery should be made.

This is accomplished by adding a "retry" flag to the appropriate HTTP utilities to control whether or not a retry should be attempted.

Adds (whisk) authenticated web actions.
Removes result projection for http actions.

Enable test.