Add API protection option for new eps limit configuration

[davidjiglesias]

As part of the development for Implement configuration limits requested by Wazuh Cloud #12512 we have finally decided to add a new configuration parameter inside ossec.conf.

We need to add a new block in API configuration to protect the edition of said parameter using Wazuh API endpoint to change ossec.conf.

The final design for the new parameters is as follows:

<global>
  <limits>
    <eps>
      <maximum>500</maximum>
      <timeframe>30</timeframe>
    </eps>
  </limits>
</global>

Also, we need to ensure the Warning message that appears when an user tries to change a protected parameter is appropriate, both for the new parameter and the old protected ones (remote commands).

[vicferpoy]

Issue update

After discussing it with the team, we have decided to fully rework this section from the API configuration. The proposed new implementation, including changes to the current syntax is the following:

upload_wazuh_configuration:
  remote_commands:
    localfile:
      allow: True
      exceptions: []
    wodle_command:
      allow: True
      exceptions: []
  limits:
    eps:
      allow: True

Before implementing the new block, we must check if there are more command blocks in the Wazuh configuration and if so, study if we should add them. For now, the exceptions clause will keep its current behavior.

[vicferpoy]

Issue update

As the API configuration has been modified, we need to update the Wazuh documentation. This also affects to our custom exceptions, as we have links to certain sections that have changed. We need to take a look at the framework exceptions once the documentation has been updated.

[davidjiglesias]

The final configuration looks as follow:

upload_configuration:
  remote_commands:
    localfile:
      allow: True
      exceptions: []
    wodle_command:
      allow: True
      exceptions: []
  limits:
    eps:
      allow: True