Add timeouts for Axum server in the Tracker API:

1. Timeout for the first request after opening the HTTP connection. 408 Request Timeout.
2. HTTP1 header read timeout. Set a timeout for reading client request headers. If a client does not transmit the entire header within this time, the connection is closed.
3. HTTP2 keep alive timeout: Sets a timeout for receiving an acknowledgement of the keep-alive ping. If the ping is not acknowledged within the timeout, the connection will be closed. Does nothing if http2_keep_alive_interval is disabled.
4. HTTP2 keep alive interval: Sets an interval for HTTP2 Ping frames should be sent to keep a connection alive.
5. Tower middleware which applies a timeout to requests.

The current implementation for the first timeout does not send any message (408 Request Timeout). It seems is also common practice.

To test the first case, you can open a connection to the API without sending any request with:

telnet 127.0.0.1 1212
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.

After 5 seconds you will see:

Connection closed by foreign host.

For advanced manual testing, you can use: https://github.com/josecelano/axum-server-timeout