Don't clear highest bit in member id string representation

[valepakh]

When looking at the logs that include string representation of the Member class, sometimes it's hard to detect differences because highest bit of the member id is cleared for some reason. We still use toHexString directly after that so there's no need to do that (if the initial intention was to see only positive values?)