Tests development - Changes in FIMDB limits configuration

[antoniomanuelfr]

Target version	Related issue	Related PR/dev branch
4.5.0	wazuh/wazuh#13988	9103-replace-fim-db-dbsync

Description

After the changes introduced in wazuh/wazuh#13988, the way the FIM DB limits are read has been changed. Now, instead of a single configuration block, the option to limit the entries from the file and registry limits has been split. The purpose of this issue is to make any necessary changes to the IT templates and tests related to the FIM database limits.

You performed the changes according to the latest changes at #2791.

We have also modified a log file when the value is disabled.
Before

(6343): No limit set to maximum number of entries to be monitored

After

(6343): No limit set to maximum number of file entries to be monitored
(6343): No limit set to maximum number of registry entries to be monitored

This change is because now we have added the enabled tag for registries, while before it was global for files and registries.

Configurations

Before

    <db_entry_limit>
      <enabled>yes</enabled>
      <files>100000</files>
      <registries>100000</registries>
    </db_entry_limit>

After

    <file_limit>
      <enabled>yes</enabled>
      <entries>50000</entries>
    </file_limit>

    <registry_limit>
      <enabled>yes</enabled>
      <entries>50000</entries>
    </registry_limit>