Rewrites need to be "remembered" to avoid repeated information for the user

[Akron]

When meta rewrites or query rewrites are shown in the user interface, these will occur for every search. This can get quite annoying, e.g. when a user searches with a default foundry like [base=Baum] and is always informed about the injected foundry when she just pages through the results.
To avoid such information overhead, messages already shown to a user need to be remembered for a session - maybe bound to a query string. A possible sollution is a list of hashes for these rewrite objects stored in the cookie or html5 client stores. When rewrites are collected from the KoralQuery, Kalamar checks, if they were already shown to the user, and only makes them visible, if they weren't.

P.S. As corpus rewrites are currently adopted by Kalamar, no repeated rewrites will occur. That's why this section isn't part of this issue.