Issue #955 suggested that the watchdog binaries should have associated sha256 files to help assure the veracity of the built artefacts.  This change mirrors the method employed on
faas-cli to generate and deploy the sha256 hash for each flavour of the current watchdog.

Signed-off-by: Richard Gee <richard@technologee.co.uk>

1. Add new annotation attributes which may be used
by the back-end for making scheduling or routing decisions.

2. Updated tests/README.md to give clearer instructions on creating and
tearing down the stack required to run the integration tests

3. Update ci.sh
 * Fail as soon as an error is encountered
 * Allow script to run locally in development environment, test if repos
are already cloned etc..
 * Deploy ./stack.yml used by existing integration tests

Signed-off-by: Edward Wilde <ewilde@gmail.com>

With this change gateway will be pushed to Quay.io on release
as a backup

Signed-off-by: Ivana Yovcheva (VMware) <iyovcheva@vmware.com>

Pipe the Docker registry password so that docker login doesn't block

Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>

CI was using a test of ! -s which appeared to give a false positive
and try to push when it shouldn't. I changed it to -z which checks
for an empty string instead.

Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>

Signed-off-by: Alex Ellis (VMware) <alexellis2@gmail.com>

use golang 1.8.3 for gateway

Signed-off-by: Minh-Quan TRAN <account@itscaro.me>

Signed-off-by: Burton Rheutan <rheutan7@gmail.com>