Move from HAProxy API Gateway to Kong

[ihatelactose]

Description

A microservices pattern is best if it supports API Gateway since using an API Gateway takes away a lot of logic that can cause issues.

Current implementation and issues

The current implementation of the API Gateway uses a community plugin that uses a JWT Verify Lua file to implement authentication and redirection to HAProxy, this might be good however provides very low features compared to a real and fully blown API Gateway.

Proposed Solution

Move to Kong, at the time of implementation we were using APISIX however that went bust due to release and simplicity reasons. However this seems perfect scenario to deploy an API Gateway that can give us exactly what we need and help with more features required by the developers using the repository!