Router/Tunnel: Handling Updates for Inbound Messages.

Eliminate the forwarding of messages in the Inbound Message Distributor.

The Inbound Message Distributor is the end point, and attempting to handling forwarding instructions opens up too many possibilities for potentially dangerous scenarios.

Typically, the messages with forwarding instructions are the result of decrypting garlic messages that yield another I2NP message, which is recursively handled.

It shouldn't be necessary to forward messages at this point. The client should handle any decisions regarding forwarding, not the router.

Normally, I don't clean up the code in a given commit, but there were some remnants of commented-out code right in the middle of the section being reworked, and this deprecated code would have been out of context if not removed.

Signed-off-by: obscuratus obscuratus@mail.i2p