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

[MakoWish]

What does this PR do?

Modify ti_rapid7_threat_command 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-21T21:55:37.667+0000

• Duration: 17 min 34 sec

Test stats 🧪

Test	Results
Failed	0
Passed	23
Skipped	0
Total	23

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

[efd6]

/test

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (3/3)	💚
Files	100.0% (3/3)	💚
Classes	100.0% (3/3)	💚
Methods	88.372% (38/43)	👎 -4.961
Lines	94.245% (868/921)	👎 -3.227
Conditionals	100.0% (0/0)	💚

[efd6]

You've found some that my automation missed, but missed the ones that I found. Can you also add changes for the default.yml files under data_stream/{alert,ioc,vulnerability}/elasticsearch/ingest_pipeline?

[MakoWish]

Oops! Forgot to change my commit message, but that last Increment version in manifest was for the three default.yml files you pointed out.

[efd6]

/test

[elasticmachine]

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