Standardised names and descriptions for security integrations

[kcreddy]

What does this PR do?

Updates the package names with standard wording

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.

Related issues

• Closes Update Security Integration Names #3400

[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: 2022-07-18T17:09:29.628+0000

• Duration: 78 min 5 sec

Test stats 🧪

Test	Results
Failed	0
Passed	1264
Skipped	1
Total	1265

🤖 GitHub comments

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

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (107/107)	💚
Files	96.729% (207/214)	👎 -0.351
Classes	96.729% (207/214)	👎 -0.351
Methods	91.751% (1813/1976)	👍 2.205
Lines	91.79% (31987/34848)	👍 1.925
Conditionals	100.0% (0/0)	💚

[jamiehynds]

Thanks for working through these changes @kcreddy. The only one I'm wary of is the httpjson input - I've pinged Serena from the Enterprise Search team, to see if we can come up with a better option. They already have a Custom API integration but hoping we can align on naming.

[zmoog]

The Azure logs part LGTM