Rename `SessionProtocolNegotiationException` to `SessionCreationTimeoutException` when session creation timed out

[Lincong]

SessionProtocolNegotiationException can be thrown from a few places in Armeria client side. However, it is more accurate to create a new type of exception named SessionCreationTimeoutException and throw it here instead of throwing SessionProtocolNegotiationException. Because SessionCreationTimeoutException is a more accurate name describing the what has gone wrong in this scenario.

Full discussion context on Discord is here. Useful info here is:

"When you make a connection attempt, a server will usually accept an incoming connection at O/S level, even if you did not call ServerSocket.accept() because OS's network stack keeps the accepted the connection it its 'backlog'. Therefore, it is practically impossible to distinguish between the two unfortunately. (Because the client will perceive the connection as established anyway unleass the server is under very high load, filling the socket accept backlog)"

[misselvexu]

/ Assign to me ?

[ikhoon]

For sure.

[misselvexu]

For sure.

I found that this problem has been solved in the latest version and this ISSUE can be turned off~ !

[ikhoon]

Is this solved? I am failing to find the related PR.