Message cache

[Th3-M4jor]

This is still a work in progress, but is the beginnings of a message cache for Nostrum.

Still needs to be hooked into the event handler and I need to test it.

Adds a new Mnesia backed message cache, but defaults to a no-op cache for most users simply because it would use a lot more memory and most users don't need a message cache.

Also improves the way pluggable caching configuration works, such that users can provide a configuration to each cache, such as configuring a maximum size or how many messages get evicted when the cache reaches its maximum size

[jchristgit]

Thanks, this looks solid already!
There is one problem with QLC that I wonder if we can contribute a smart fix for upstream: qlc:keysort will always sort the entire table (as a list) in memory, so it's not exactly efficient on big tables. For large message caches this would mean a temporary bloating of memory on every cull. For the other "sorted by age" queries I think it's fine.
Should we maybe change the cull of old messages somehow differently... I'm thinking.. maybe we can memorize the oldest message somehow, but then we have to somehow update it - how would that work - or we need to, hm, I wonder

[Th3-M4jor]

Still need to do some real testing of it myself but other than that, this should be ready.

Do note that there are breaking changes that come with this

[jchristgit]

Using an eviction count instead of always deleting the last message is pretty smart, nice!

I have a question, there is a lot of sorting going on, should we perhaps use an ordered_set table instead to just have it sorted by the primary key out of the box?

[jchristgit]

Solid work!

I think I forgot to bring this up before: what do you think about using ordered_set for the cache, such that the messages are sorted by message ID by default, and we do not need to sort results everywhere? This should also speed up culling old messages if I'm not wrong.

[jchristgit]

This is really nice, thank you!!!!

[jchristgit]

Thanks!