bitmask-vpn uses wrong protocol and port combination

In v3 eip-service.json we have the following json for a gateway's transport (gateways[].capabilities.transport):

{
    "transport": [
      {
        "ports": [
          "53",
          "80",
          "1194"
        ],
        "protocols": [
          "tcp",
          "udp"
        ],
        "type": "openvpn"
      }
    ]
}

client should use port 53 with tcp and 80, 1194 with udp, this depends on the order of the elements in the array, but currently bitmask-vpn is not considering this and using 53 with udp or 1194 with tcp