Improve the reading of the IP addresses from the config.yml file

[rauldpm]

Description

The config.yml configuration file specifies an IP format of the form ip: <indexer-node-ip>, where <indexer-node-ip> must be replaced by the IP address (including <>), this is not specified in the documentation and we delegate to the users the part where it is understood that the characters < and > must be replaced since they are used as markers.

To avoid this, we should only specify a more understandable option where if there is a delimiter character it is also accepted, for example:

• ip: indexer-node-ip
• ip: "indexer-node-ip"

Another option would be to modify the Wazuh installation assistant so that it removes the delimiter characters in case they are entered.

Related: https://www.reddit.com/r/Wazuh/comments/11xcy7b/wazuh_installation_assistant_indexer_installation

[CarlosALgit]

Update Report

I've been reading the code and trying some solutions to this, but the regex is hard to understand and to tune.

[CarlosALgit]

Update Report

The changes have been made and pushed to the branch. The tests are passing okay. It remains to do more tests and talk with the team where can the changes impact if I'm missing something.
I pass this issue to On Hold due to reasons above and to prioritise https://github.com/wazuh/wazuh-automation/issues/1954

[CarlosALgit]

Update Report

The team is reviewing these changes in order to double check if I'm missing impact somewhere.

[CarlosALgit]

Update Report

After reviewing these changes we think that allowing the IP to be betweeen < > is a bad solution due to the standard for updating fields from the user side is letting the < > in the specified field.

So, the solution we see is to improve the error output to make it clearer when the IP is wrote between < >.

However, the Cert Tool may not be supported from 5.0 onwards, so for now the issue remains blocked.

[teddytpc1]

Javi: The cert tool must exist (it should be improved actually) and owned by DevOps.