Make support for admin systems cleaner and easier

[BadgerCode]

There have been multiple PRs to add support for new admin systems

• SAM: Added waiting for staff and fixed sam #69 replace ulx with sam there #42 Slay message is missing admin name #41 Update autoslay.lua #43 add sam support #40
• sAdmin: sAdmin support #87

Currently the code to add support for an admin system is scattered across the project.

• All of the code to implement support for a specific admin system should ideally be in one file, or one folder
• Each admin system integration should implement all of the required functionality for the damage logs (like an interface/class)
• The rest of the damage logs shouldn't know anything about which admin system it is using; it just calls a common interface for interacting with admin systems
• Selecting which admin system to use should be done via configuration

[wgaylord]

Would https://github.com/glua/CAMI be useful for this?

[BadgerCode]

Would https://github.com/glua/CAMI be useful for this?

It would depend on whether all of the admin systems supported implement CAMI I believe.

It seems most of the functionality can be found in two files

• lua/damagelogs/client/tabs/rdm_manager.lua
• lua/damagelogs/shared/autoslay.lua

I think this code could be massively simplified, making it easier to add support for new admin systems.
We could even add support for admin systems that implement "CAMI"

[BadgerCode]

I can also see some references to ULX in lua/damagelogs/server/autoslay.lua

And some config- ULX_AutoslayMode, ULX_Autoslay_ForceRole

[wgaylord]

Working on this, Started by pulling the admin addon related command stuff out to the respective admin module folders that those addons use to load new commands normally. This breaks up the ULX, SAM and sAdmin code for making the commands into their own files. https://github.com/wgaylord/tttdamagelogs/tree/cleanup_admin_stuff