Options section for integrations.

[GabrielEValenzuela]

Description

This PR addresses and closes #5927 . It expands on the integrations examples using the new feature options.

With the changes to this PR, the following issues would be fixed:

• Allow Slack notifications customization wazuh#14479

The changes that have been made are as follows:

• Add new tag inside integrations, called options that supports a custom JSON object to add or modify the different tags of the integrations.

<options>JSON</options> <!-- Replace with your custom JSON object -->

• Add links to the different APIs so that the user has direct access to the fields he can modify.
• Add a quick example to the ossec.conf reference.

Checks

• Compiles without warnings.
• Uses present tense, active voice, and semi-formal registry.
• Uses short, simple sentences.
• Uses bold for user interface elements, italics for key terms or emphasis, and code font for Bash commands, file names, REST paths, and code.
• Uses three spaces indentation.
• Adds or updates meta descriptions accordingly.
• Updates the redirects.js script if necessary (check this guide).

[MarcelKemp]

It is necessary to add a Shuffle API reference that has the variables that can be modified for the options field.

[javimed]

@GabrielEValenzuela

• If this is meant for 4.7.0 release, the base for the PR needs to be 4.7.0 and not master.
• In user-manual/reference/ossec-conf/integration.html#configuration-example, rather than showing <options>JSON</options> <!-- Replace with your custom JSON object --> we could show a specific use example, e.g. <options>{"pretext": "Custom Title"}</options> <!-- Replace with your custom JSON object --> for a Slack configuration example.

[GabrielEValenzuela]

@javimed

Thanks Javi, the changes have been applied correctly 😃

[javimed]

What new script? maybe some context is needed if commenting like this

[GabrielEValenzuela]

Hi @javimed !

I spoke with @MarcelKemp and the new script is being maintained.

Mainly, the change is based on the fact that pagerduty previously had a shell script and now it is in python.
For this reason, as most of the python scripts of integrations, the format of the alert that it expects is in JSON and for this reason it is necessary to change this parameter in the configuration.

Here I let you the associate PR and issue 😃

Let's revise that mandatory json format comment in the configuration