[FEATURE] Allow arbitrary RCon commands in chat commands

[FlorianSW]

There are communities that would like to use chat commands with a more powerful set of actions that can be triggered when a player uses a chat command. Two real-worl example from the "event server for prepping" use case:

Switching player side

Changing a side without needing to redeploy for themself, a command "!switch" is useful. Issuing this command will forward a switch_player_now RCon command with the player_name of the issuing player.

Redeploying with 10 instead of 20 seconds

Redeploying with the punish command might be useful when needing to redeploy for multiple times. A command "!redeploy", which issues a punish command for the issuing player, might be useful here.

This feature is implemented with this PR. A chat command can either have a message key or a command key (message takes precendence). The command config is an object that has the same signature and functinality as auto-settings commands.
This allows for a powerful set of tools, while it also has some risks, as everything can now be executed with a player issuing a specific chat command.

The parameters of the command will replace message parameters same as the message itself, however, only context keys are populated. No other variables are available in commands params.

Example config

{
  "enabled": true,
  "command_words": [
    {
      "words": [
        "!switch"
      ],
      "message": null,
      "commands": {
        "switch_player_now": {
          "player_name": "{player_name}"
        }
      },
      "conditions": {
        "player_id": {
          "player_ids": [
            "765611..."
          ]
        },
        "online_mods": {
          "max": 10,
          "min": 0
        },
        "player_flag": {
          "flags": [
            "👍"
          ]
        },
        "player_count": {
          "max": 10,
          "min": 0
        }
      }
      "enabled": true,
      "description": "Switch yourself in side"
    },
    {
      "words": [
        "!admin"
      ],
      "message": null,
      "commands": {
        "add_admin": {
          "role": "junior",
          "player_id": "{player_id}",
          "description": "{player_name}"
        }
      },
      "enabled": true,
      "description": "Add yourself to admin cam list"
    }
  ],
  "describe_words": []
}

Conditions

As seen in the above example, conditions are available for these commands. This allows an admin to define commands which are only executed when the execution context matches certain conditions. These conditions are the same as in AutoSettings.
The PR adds two new conditions, which are only available when the metric source player_id is available. This metric source is currently only available in chat commands, not in auto settings. In auto settings, if one of these conditions is configured, it will always default to "condition is met".

• Player Flags: The player flags condition is met, when the executing player has at least one of the flags configured in the condition. Otherwise, the condition is not met.
• Player ID: The condition is met, when the player's ID (Steam ID or Windows ID hash) is one of the configured ones

Automatic enablement and disablement

To make commands only available under certain conditions, a new api is available for auto settings, an example::

{
  "always_allow_defaults": true,
  "defaults": {
    "set_chat_command_enabled": {
      "word": "!switch",
      "enabled": true
    }
  },
  "rules": []
}

This api can be used with all the available conditions in the rules section as known for the other stuff..