Create a troubleshooting guide for vulnerability detector module

[pereyra-m]

Description

This PR proposes a new troubleshooting module section that contains:

• FAQ: we can include here all the problems we find regularly solving communities question that aren't related to a problem in the module but a configuration issue.
• Known issues: the description of the problems that have a fix released an a workaround.

If the proposal is out of scope or requires more revision/approval, I can simply add the already written guide to the upgrade guide (as the issue proposes) and create another issue.
I think that the upgrade guide isn't the best place to add this vulnerability detector problems, and a proper label and description of each situation is required (see each table).

I've added a communication problem with the Indexer as an example of a FAQ.

The final result can be seen by compiling the branch, here I upload some snapshots

Details

Checks

Docs building

• Compiles without warnings.

Code formatting and web optimization

• Uses three spaces indentation.
• Adds or updates meta descriptions accordingly.
• Updates the redirects.js script if necessary (check this guide).

Writing style

• 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.

[sebasfalcone]

Partial review

[sebasfalcone]

I've compiled the documentation and it looks really good, great work with the tables and highlights in the code blocks!

[Dwordcito]

LGTM, assigned to @wazuh/devel-qa team for final review.

@sebasfalcone push this.

The base branch was changed.

[sebasfalcone]

LGTM!

I've compiled the documentation, looks good in the browser