Create ForgeRock integration

[kgeller]

What does this PR do?

Adds a new integration for ForgeRock Identity Platform.

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 Note

I've reworked this integration from when I initially put it out for review. I now have individual data streams for each source from ForgeRock, and have fixed the issues I had with paging.

How to test this PR locally

Below is a link to a development config and a postman collection for the API.

https://drive.google.com/file/d/1EZht-ycUrG6rp2PmswXgiUPhJFdMdJS9/view?usp=share_link

Related issues

Closes #1085

Screenshots

Demo

https://drive.google.com/file/d/1F8WjLBLLMOromoTtX2wsLm-s4IrPDszd/view?usp=sharing

[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-01-11T18:02:40.013+0000

• Duration: 23 min 47 sec

Test stats 🧪

Test	Results
Failed	0
Passed	56
Skipped	0
Total	56

🤖 GitHub comments

Expand to view the 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% (11/11)	💚
Files	100.0% (11/11)	💚
Classes	100.0% (11/11)	💚
Methods	100.0% (101/101)	💚 75.0
Lines	96.489% (962/997)	👎 -3.511
Conditionals	100.0% (0/0)	💚

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[kgeller]

/test

[taylor-swanson]

Still looking through everything, but a couple of quick comments.

[taylor-swanson]

I would make the change for GA in the manifest, but otherwise LGTM.

[taylor-swanson]

One other thing I noticed, the exported fields section in Kibana is showing "no fields available". I'm not sure if that's an issue with my kibana or how I built it, but seems odd that's missing.

[kgeller]

One other thing I noticed, the exported fields section in Kibana is showing "no fields available". I'm not sure if that's an issue with my kibana or how I built it, but seems odd that's missing.

Oh good catch! I forgot to update these after switching from one datastream to individual. Should be updated now.

[elasticmachine]

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