[Windows] Ensure event.kind is correctly set for pipeline errors

[MakoWish]

What does this PR do?

Modify forwarded data stream for windows integration to correctly set event.kind for pipeline errors and ensure error.message is an array.

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.
• I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

•  

How to test this PR locally

Related issues

• For sei: ensure packages set error.kind to "pipeline_error" in on_failure processor #6582

Screenshots

[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: 2023-06-19T23:16:12.936+0000

• Duration: 16 min 51 sec

Test stats 🧪

Test	Results
Failed	0
Passed	129
Skipped	0
Total	129

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

[MakoWish]

Ugh... why are files from AWS being included in the commit when viewed here? I didn't touch those, and they are not shown in my original commit:

[efd6]

/test

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (4/4)	💚
Files	87.5% (7/8)	👎 -9.53
Classes	87.5% (7/8)	👎 -9.53
Methods	83.696% (77/92)	👎 -8.456
Lines	92.813% (5153/5552)	👍 0.898
Conditionals	100.0% (0/0)	💚

[elasticmachine]

Package windows - 1.24.0 containing this change is available at https://epr.elastic.co/search?package=windows