Correctly allocate the NetVaultNode in pyVaultPlayerInfoListNode.

The affected code was ported from H'uru where NetVaultNode has a zeroing
constructor. OU does not have a zeroing constructor for this class, and
instead assumes that all allocations will be done with NEWZERO (there is
a debug mode assertion to this effect). The result of the improper
allocation is that the node fields flag could be garbage, causing a
vault node with random contents to be written to the server.

Unfortunately, NetVaultNode::Read_LCS is not extremely resilient to
reading in unexpected data, so this may result in a crash.

Sources/Plasma/FeatureLib/pfPython/pyVaultPlayerInfoListNode.cpp

@@ -107,7 +107,7 @@ void pyVaultPlayerInfoListNode::AddPlayer( UInt32 playerID )
 	if (HasPlayer(playerID) || !fNode)
 		return;
 
-	NetVaultNode* templateNode = new NetVaultNode();
+	NetVaultNode* templateNode = NEWZERO(NetVaultNode);
 	templateNode->IncRef();
 	templateNode->SetNodeType(plVault::kNodeType_PlayerInfo);
 	VaultPlayerInfoNode access(templateNode);