Passthrough needs to track create/destroy/etc operations for re-send

[jd0-sag]

(migrated from Terracotta-OSS/terracotta-apis#107, after the corresponding code moved here)

Similarly to how the multi-process server tracks these, in order to cache the result of re-sent internal messages, passthrough needs to do the same, now that retire support makes it possible to see re-sent messages in more cases.

Intermittent failures with the following stack trace have been observed which seems to imply a double-create, on re-send:
at org.terracotta.passthrough.PassthroughServerProcess.create(PassthroughServerProcess.java:648) at org.terracotta.passthrough.PassthroughServerMessageDecoder.decode(PassthroughServerMessageDecoder.java:99) at org.terracotta.passthrough.PassthroughServerMessageDecoder.decode(PassthroughServerMessageDecoder.java:35) at org.terracotta.passthrough.PassthroughMessageCodec.runRawDecoder(PassthroughMessageCodec.java:399) at org.terracotta.passthrough.PassthroughMessageCodec.decodeRawMessage(PassthroughMessageCodec.java:322) at org.terracotta.passthrough.PassthroughServerProcess.serverThreadHandleMessage(PassthroughServerProcess.java:465) at org.terracotta.passthrough.PassthroughServerProcess.runServerThread(PassthroughServerProcess.java:441) at org.terracotta.passthrough.PassthroughServerProcess.access$000(PassthroughServerProcess.java:75) at org.terracotta.passthrough.PassthroughServerProcess$2.run(PassthroughServerProcess.java:208) at java.lang.Thread.run(Thread.java:745)