Test decoders before matching rules

[sortiz1191]

Hi team!
This PR adds a feature to check decoders and rulesets using logtest.

To test it:

1. Go to Management/Decoders

• Given the browser is logged in the Wazuh kibana app
• When the browser enters Management/Decoders
• Then Decoders Sections will be displayed

Prerequisite 1: command: Apr 28 13:43:51 localhost local_decoder_example: test

2. Test a decoder

• Given the browser is at Decoder section
• When the user navigate to custom decoder -> Add new decoder file -> Decoder test
• And the user paste Prerequisite 1 and click in test
• Then Decoders Test Section will not display an error

Tests:

The cases in focus are:

• a log sample that matches a decoder but that matches no rule
• a log sample that matches a rule that is level 0 (which always suppresses alerts)
• a log sample that matches a rule that is level 1 or 2 (which generally is not logged due to default setting <log_alert_level>3</log_alert_level> in ossec.conf )

All of the above cases should produce the same output in the web interface as they currently output when wazuh-logtest is run from the command line.

Here is an example of the second item. It only matches top level parent rule 5700 which is level 0.

Starting wazuh-logtest v4.2.4
Type one log per line
Nov  5 10:20:01 my-server sshd[529099]: this will get decoded but only match a level 0 rule

**Phase 1: Completed pre-decoding.
        full event: 'Nov  5 10:20:01 my-server sshd[529099]: this will get decoded but only match a level 0 rule'
        timestamp: 'Nov  5 10:20:01'
        hostname: 'my-server'
        program_name: 'sshd'
**Phase 2: Completed decoding.
        name: 'sshd' 

As to the first item in my list, I am assuming this is already present in local_decoder.xml

<decoder name="local_decoder_example">
    <program_name>local_decoder_example</program_name>
</decoder>

And here an example of a non-rule-matching sample that matches a decoder

2021/11/05 10:36:19 wazuh-testrule: INFO: Started (pid: 2391674).
Since Wazuh v4.1.0 this binary is deprecated. Use wazuh-logtest instead
wazuh-testrule: Type one log per line.
Nov  5 10:20:01 my-server local_decoder_example[12345]: this will get decoded but match no rule at all

**Phase 1: Completed pre-decoding.
       full event: 'Nov  5 10:20:01 my-server local_decoder_example[12345]: this will get decoded but match no rule at all'
       timestamp: 'Nov  5 10:20:01'
       hostname: 'my-server'
       program_name: 'local_decoder_example'
       log: 'this will get decoded but match no rule at all'
**Phase 2: Completed decoding.
       decoder: 'local_decoder_example'

Lastly an example of a level 2 rule that would normally not be logged:

  <rule id="5753" level="2">
    <if_sid>5750</if_sid>
    <match>no matching cipher found</match>
    <description>sshd: could not negotiate with client, no matching cipher.</description>
  </rule>

Here that one goes:

Starting wazuh-logtest v4.2.4
Type one log per line
Nov  5 10:20:01 my-server sshd[12345]: fatal: no matching cipher found

**Phase 1: Completed pre-decoding.
        full event: 'Nov  5 10:20:01 my-server sshd[12345]: fatal: no matching cipher found'
        timestamp: 'Nov  5 10:20:01'
        hostname: 'my-server'
        program_name: 'sshd'
**Phase 2: Completed decoding.
        name: 'sshd'
**Phase 3: Completed filtering (rules).
        id: '5753'
        level: '2'
        description: 'sshd: could not negotiate with client, no matching cipher.'
        groups: '['syslog', 'sshd']'
        firedtimes: '1'
        mail: 'False' 

Related issue: #3348

[mpRegalado]

You accidentally branched from e4399fe and so the changes on the feature/3391_office365_module_navigation branch are included in this PR.
You should probably rebase it.

[Desvelao]

issue: There are changes related to the Office 365 module. We should remove these changes to the PR.

nitpick: Add the change to the changelog

[mpRegalado]

CR: LGTM: ✔️

[Desvelao]

Changes

• Add change to the changelog

[Desvelao]

review:
Code Review ✅

[github-actions]

Jest Test Coverage	%	values
Statements	3.12%	( 1109 / 35600 )
Branches	1.16%	( 324 / 27965 )
Functions	2.02%	( 174 / 8632 )
Lines	3.15%	( 1071 / 34018 )