GroupManager#getAllGroupNames runs on main thread

[okx-code]

This is a database call and should not run on the main thread. It's used by several tab completion commands.

[Diet-Cola]

GroupManagerDao has an abundance of async methods for every call, Do we want to switch to using these or can we just clean them up and remove them? I think its left over from Civcraft 3.0 sharding with Mercury

[Protonull]

Do we want to switch to using these or can we just clean them up and remove them?

I'd argue that those kinds of methods, the ones that do nothing but invoke the sync-version within a scheduler, should just be removed: the scheduling should be done by the caller, not the method. Granted, this is more of a stylistic preference because at least the methods are suffixed with "async" so nothing is being obscured, but still, there's a whole load of bytecode clutter in these dao classes that are just async duplicates of functions.