Improve interoperability of commands by changing action.args to object

[AlexRuiz7]

Description

Related issue: #349

Currently, the action.args fields of commands is an array, which fits good enough the existing use cases for the MVP phase. However, this data structure has proven to be insufficient / limited for more complex commands. For this reason, we are changing the action.args to object. The fields of this object are to be defined ad-hoc for each kind of command. The definition of these commands needs to be depicted by the @wazuh/devel-agent team. For now, we'll not validate or fix the fields under this object, so the commands index needs to be temporarily set to dynamic in order to accept any nested fields. The remaining fields are unchanged.

This change needs to be applied on agent, server and indexer.

{
    "orders": [
        {
            "action": {
                "args": {},
                "name": "restart",
                "version": "5.0.0"
            },
            "source": "Users/Services",
            "document_id": "A8-62pMBBmC6Jrvqj9kW",
            "user": "Management API",
            "target": {
                "id": "d5b250c4-dfa1-4d94-827f-9f99210dbe6c",
                "type": "agent"
            }
        }
    ]
}

Functional requirements

• The commands.action.args field is an object.
• The fields under commands.action.args are dynamic (any nested field is accepted).
• The Wazuh Agent receives commands and the result arrives back to indexer.
• The Command Manager API also receives the field as an object.

Implementation restrictions

• The remaining fields are unchanged.

Plan

• Update index model and documentation.
• Update index template on the setup plugin and tooling.
• Update Management API commands (orders) schema.
• Update Agent commands (orders) schema.