BungeeCord protocol support

Some kind of protocol support for BungeeCord in node-minecraft-protocol might be interesting.

It sends additional information in the set_protocol packet host field, in the same way as Forge (which instead appends \0FML\0 https://github.com/PrismarineJS/node-minecraft-protocol/issues/114, called this tagHost in https://github.com/PrismarineJS/node-minecraft-protocol/pull/326)

Stumbled across this in Cuberite:

    // BungeeCord handling:
    // If BC is setup with ip_forward == true, it sends additional data in the login packet's ServerAddress field:
    // hostname\00ip-address\00uuid\00profile-properties-as-json
    AStringVector Params;
    if (cRoot::Get()->GetServer()->ShouldAllowBungeeCord() && SplitZeroTerminatedStrings(a_ServerAddress, Params) && (Params.size() == 4))
    {
        LOGD("Player at %s connected via BungeeCord", Params[1].c_str());
        m_ServerAddress = Params[0];
        m_Client->SetIPString(Params[1]);
        m_Client->SetUUID(cMojangAPI::MakeUUIDShort(Params[2]));
        m_Client->SetProperties(Params[3]);
    }

https://github.com/PrismarineJS/node-minecraft-protocol/issues/145 BungeeCord : Fails to parse - closed, not known if still applicable
https://github.com/PrismarineJS/node-minecraft-protocol/issues/302 - a potential use case

Start by reviewing how node-minecraft-protocol handles the set_protocol host field and the existing Forge tagHost work referenced in issue 114 and pull request 326. Check closed issue 145 and issue 302 for prior context, then clarify the intended BungeeCord behavior and define tests for parsing its additional login data before implementation.