Add option to disable pod events enrichment with deployment name

[ChrsMark]

What does this PR do?

This is a "backport" of #28521 so as to support disabling of Deployment metadata enrichment in Pod events.

This will allow us to disable the enrichment that in large clusters can cost a lot and push the k8s API server.

@gizas @tetianakravchenko what do you think?

[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-12-22T13:39:54.473+0000

• Duration: 84 min 30 sec

Test stats 🧪

Test	Results
Failed	0
Passed	22222
Skipped	1562
Total	23784

💚 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!)

[gizas]

Should not this be false?

[ChrsMark]

Prior to this, it works like "true" be default so we need to preserve it as is and just give the option to disable it when users actually need this.

[gizas]

thanks

[tetianakravchenko]

LGTM!
just one documentation comment

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[ChrsMark]

I have tested locally the changes to verify we don't miss anything important with this backport. Everything works as expected:

deployment: true (default state)

deployment: false