Client-side filtering of messages

[HashMapsData2Value]

While the long-term solution should be using custom Indexer/Conduit to create an Edaga bespoke node backend to pull the transactions, for now we can start with client-side filtering:

Allow for the user to ignore/filter away messages based on:

• - A message containing certain keywords, e.g. slurs or spam.
• - The transaction not reaching a certain minimum fee. (I fully expect bots to spam the hell out of the public space, so to make it more expensive a user can ensure their message rises above the spam by paying a higher minimum fee.)
• - Being from a certain address. (Though this can be trivial to circumvent.)