Refactoring: use faas-provider model package

Move to faas-provider models

Moves to use models from faas-provider instead of from the
gateway package.

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>

Update Go to 1.11 and Dockerfile runtime to Alpine 3.10

Changelog:

• Update Go to 1.11 and Dockerfile runtime to Alpine 3.10 #54 @LucasRoesler
• Update sys modules to support Risc-V #52 @carlosedp
• Use multi-arch version of license-check - 9dac977 @alexellis

Add logs support in API

Changelog:

• Add logs support #47 via @LucasRoesler

Updates healthcheck endpoint

Changelog:

• Updates healthcheck endpoint #49 @ewilde

Return empty list when no secrets present in API

Return empty list when no secrets present in API #44

Add secrets CRUD

Changelog:

• Added secret handler #42 @bartsmykla @LucasRoesler @alexellis

Vendor faas-provider for proxying to functions

Changelog:

• Vendor faas-provider for proxying to functions #39 via @LucasRoesler

This change should largely be a no-harm change and only affects gateways which have direct_functions set to false meaning every function invocation first passes through the provider.

Return 202 instead of 200 for CRUD

Changelog:

• Return 202 instead of 200 for CRUD via #25 #33 @viveksyngh

Expand HTTP methods for proxying through provider

This change does not affect most users, it is only used when direct_functions is set to false and function calls pass through the provider.

Enable basic auth on incoming calls

Changelog:

• Enable/enforce basic auth #31 #32

When "basic_auth" is set to true as an env-var, all incoming calls to the /system/ routes are protected with the basic auth credentials in the cluster.