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.

- No longer decode action invocation response into structs

* Add kafka_python library to the Python action runtime

* Update doc and Python package sniff test

Please squash into previous commit

* set fileHandleLimit to 1024 and add testcase

* Make test tighter.

* Handle application error (handled exception).

If the activation result is an activation error, treat it like a successful
activation with one distinction: rather than projecting the result per the
path specified in the URL, project only the error field. The resulting JSON
value must be of the expected type otherwise, an appropriate error is reported.

This change will allow an HTTP response to set it own status code on error
for example, but also means that the action producing the error response must
be aware of the extension type.

The extension type is not passed to the action - perhaps it should be. Even so,
in the case of a sequence, one would need to forward this type to individual
components to handle the error case (or result) correctly.

Add tests for failure to activate because of the throttles.

* Tighten extension match, add matcher unit test.

* Consolidate extension maps.

* Remove print, fix typo.

* Fix log format of logged responses

* Add Akka Logging to OpenWhisk

* Code review comments

- Display proper error message during a blocking invocation when result flag is being used