when cli act as server with client authentication, it sends NewSessionTicket directly after Finished

In https://github.com/h2o/picotls/issues/10, explain the reason why picotls could send NewSessionTicket before receiving ClientFinished.

'Although the resumption master secret depends on the client’s second flight, servers which do not request client authentication MAY compute the remainder of the transcript independently and then send a NewSessionTicket immediately upon sending its Finished rather than waiting for the client Finished.'

But when cli act as server with argument '-a', it still send NewSessionTicket before receiving ClientFinished.

Start by reproducing the CLI server behavior with client authentication enabled using the -a argument. Trace when NewSessionTicket is sent relative to ClientFinished, using issue #10 and the quoted TLS 1.3 guidance as context. Done means the authenticated server no longer sends the ticket before receiving ClientFinished.

Written by the indexing model from the issue text.