GWRequestHandler: rename registration thread after verification
GWRequestHandler: rename registration thread after verification

With the previous thread-naming scheme, we would get:

ws-127.0.0.1:37858 [Information] connection from 127.0.0.1:37858
gws-register-1284174504043136 [Notice] gateway 1284174504043136
		was accepted in relaxed mode
gws-register-1284174504043136 [Information] created connection
		to 1284174504043136

There is missing the obvious connection between the peer address
and the gateway ID so it is difficult to match them. (It is still
possible by using the thread ID but this way is better for manual
checks).

After this change, we would see:

ws-127.0.0.1:37858 [Information] connection from 127.0.0.1:37858
ws-127.0.0.1:37858 [Notice] gateway 1284174504043136 was accepted
		in relaxed mode
gws-register-1284174504043136 [Information] created connection
		to 1284174504043136

Signed-off-by: Jan Viktorin <3eab6ac54c005c4408f608556a6663b7f2abede7@fit.vutbr.cz>

BeeeOn/server,BeeeOn/server,BeeeOn/server,BeeeOn/server