Fix processors configuration in windows and o365 packages

[adriansr]

What does this PR do?

Fixes the processors configuration option for windows and o365 packages.

Before this change, trying to add custom processors to any of their data streams resulted in the following error:

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• [ ] If I'm introducing a new feature, I have modified the Kibana version constraint in my package's manifest.yml file to point to the latest Elastic stack release (e.g. ^7.13.0).

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[andrewkroh]

LGTM, but I did have a question.

[andrewkroh]

This is using if processors.length while others are using if processors. Any idea why? And could we change this one to be consistent with the others without impacting behavior.

[adriansr]

I see we have 300 usages of if processors and 10 for processors.length. I have no idea what the difference is but both worked fine in my tests.

For now I think it's better to leave this PR as is, each package using its original condition, and evaluate separately if we need to change all packages to use the better of the two kinds of conditions.

/cc @marc-gr as I think he added all the processors.length conditions.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2021-11-02T18:26:53.888+0000

• Duration: 17 min 13 sec

• Commit: cac0ab0

Test stats 🧪

Test	Results
Failed	0
Passed	152
Skipped	0
Total	152

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.