Add elastic/obs-cloud-monitoring to own cloud-related processors

[rdner]

So, the code reviews are assigned properly.

According to @jlind23 the cloud metadata processor belongs to @elastic/obs-cloud-monitoring
and the Kubernetes metadata processors belongs to @elastic/obs-cloudnative-monitoring

I occasionally see PRs that are assigned to the data plane team but they're about internals of these two processors. I think it would be better if the owning teams review them.

I might be wrong about this ownership, if so, please leave a comment.

[botelastic]

This pull request doesn't have a Team:<team> label.

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @rdner? 🙏.
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-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

[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-05-15T07:52:26.326+0000

• Duration: 12 min 30 sec

Test stats 🧪

Test	Results
Failed	0
Passed	3
Skipped	0
Total	3

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[jlind23]

Thanks for the update.