MPX-67 - Refactor mProxy

[dborovcanin]

What does this do?

This pull request makes mGate a standalone proxy separate handlers for different protocols.

Which issue(s) does this PR fix/relate to?

This pull request resolves #67.

List any changes that modify/break current functionality

• mPorxy is not a library anymore
• all the internal API significantly changed
• mProxy is SuperMQ-native now - default handlers are acting as SuperMQ PEP

Have you included tests for your changes?

No, it will happen in a separate PR.

Did you document any new/modified functionality?

No, docs PRs are also following in the near future.

Notes

N/A

[dborovcanin]

Closing in favor of #1.

[arvindh123]

The PR Looks good,
It will be great if we have following feature in Proxy, since all other modern proxies these featuers

• Hot reload (important feature, all others are providing hot reload)
• Configuration via YAML file
• Add Protocol via Plugin like HTTP, MQTT,
• Add other features like Rate Limit, band wdith control via Plugin
• Configurable everything thing via REST API

Example Config file:

listeners:
  - name: http
    protocol: http
    type: tcp
    port: 8080
    tls:
      enabled: true
      cert_file: certs/server.crt
      key_file: certs/server.key
      mtls:
        enabled: false

  - name: mqtt
    protocol: mqtt
    type: tcp
    port: 8883
    tls:
      enabled: true
      cert_file: certs/mqtt.crt
      key_file: certs/mqtt.key
      mtls:
        enabled: true
        ca_file: certs/ca.crt

  - name: coap
    protocol: coap
    type: udp
    port: 5684
    dtls:
      enabled: true
      cert_file: certs/coap.crt
      key_file: certs/coap.key
      mtls:
        enabled: true
        ca_file: certs/ca.crt

plugins:
  http: ./plugins/http.so
  mqtt: ./plugins/mqtt.so
  coap: ./plugins/coap.so