Refactor ActivityMap

[Aleksey-Terzi]

The goal of this change is to improve performance of the server and decrease amount of used resources (first of all load on the database)

1. Added support for load/unload functionality (in a similar way CMC ChunkMeta does)
2. It loads into the memory only those regions that belong to loaded chunks and unload those that are not used by loaded chunks
3. activity-map-resolution should be multiple of 16 i.e. aligned with chunk size
4. Only one thread is loading regions and only one thread is saving regions
5. Introduced a new command am stat (permission citadel.admin) that shows ActivityMap statistic:

[Diet-Cola]

Very cool and clear as always

[Protonull]

There's no need for .equals() or .hashCode() on records unless you're doing something very custom

[Aleksey-Terzi]

equals - agree
hashCode - I want to have here my own hashing function

[Protonull]

It's better to do Component.text("Message", colour);

What you're doing here is creating a new component with the text "[ActivityMap] region load statistics:", then creating another component that has that text but also the colour YELLOW. So you're creating two components here, not one.

[Aleksey-Terzi]

This function will be called like 0 - 4 times per day so I think doubled components are not a problem here.
I like a separate color more :)

[Protonull]

Oh yeah, it's not the end of the world. Since you aren't fussed and prefer the separation, you could also do

Component.text()
    .color(NamedTextColor.YELLOW)
    .content("[ActivityMap] region load statistics:")
    .build()

as Component.text() returns a builder which you can modify as much as you like.

[okx-code]

This adds a significant amount of complexity for what is essentially optimistically loading chunks from the database, why is this necessary?

[Aleksey-Terzi]

This adds a significant amount of complexity for what is essentially optimistically loading chunks from the database, why is this necessary?

We have at the moment 3 main problems:

1. ActivityMap creates too many async tasks which use too many connections. This makes problems not only for ActivityMap by itself but also for other functionality in Citadel that uses connections like reading reinforcements from DB.
2. ActivityMap creates too many updates, we don't need to update group regions if they have been updated recently. Imagine a bunch of players with similar groups running together. Also, it is enough to update ActivityMap once per 1 - 3 hours, in the scope of 2 months - this is nothing.
3. ActivityMap very often doesn't contain the required information and it is needed to load data from DB in "main thread"

For example, the recent RB problems were related indirectly to ActivityMap - ActivityMap occupied all connections, Citadel was not able to load reinforcements, this slowed down loading ChunkMeta and RB was not able to get data in time.