Let network processor handle multiple IPs

[fearful-symmetry]

Proposed commit message

This fixes a bug where the network processor would simply fail if it was given a document that had a list of IPs instead of a single IP. This uses "any match is a match" logic and instead traverses the list of IPs, if there is one.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Issue

#41917

[elasticmachine]

Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform)

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @fearful-symmetry? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit

[mergify]

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

[leehinman]

LGTM, just the one change in the changelog from processor to condition

[andrewkroh]

The documentation for the processor should be updated to indicate the behavior for arrays.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b network-processor-handle-ips upstream/network-processor-handle-ips
git merge upstream/main
git push upstream network-processor-handle-ips