[envoyproxy][mongodb_atlas] Update failing mappings when validation based on mappings enabled

[mrodm]

Proposed commit message

Updated failing mappings found for envoyproxy and mongodb_atlas packages when elastic-package uses validation based on mappings.

envoyproxy

Added missing mappings for envoy.thread_local_cluster_manager metrics.
Added the same mappings as the other groups (mean, min, max, count and so on).

Example of error found (buildkite link):

test case failed: one or more errors found in mappings in metrics-envoyproxy.stats index template:
[0] field "envoy.thread_local_cluster_manager.worker_0_clusters_inflated.value" is undefined: field definition not found

mongodb_atlas

Update flattened field definitions to not create dynamic templates.

As they were previously, this dynamic template is created:

      "dynamic_templates": [
        {
          "mongodb_atlas.project.additional_info.*": {
            "path_match": "mongodb_atlas.project.additional_info.*",
            "match_mapping_type": "object",
            "mapping": {
              "type": "flattened"
            }
          }
        },
      ]

With the change of this PR, this mapping is created as:

        "mongodb_atlas": {
          "properties": {
            "project": {
              "properties": {
                "additional_info": {
                  "type": "flattened"
                },
              },
            },
          },
        },

Example of errors found (buildkite link):

test case failed: one or more errors found in mappings in logs-mongodb_atlas.project index template:
[0] field "mongodb_atlas.project.additional_info._t" is undefined: field definition not found
[1] field "mongodb_atlas.project.additional_info.cid" is undefined: field definition not found
[2] field "mongodb_atlas.project.additional_info.cre" is undefined: field definition not found
[3] field "mongodb_atlas.project.additional_info.description" is undefined: field definition not found
...

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.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Run elastic-package with mappings validation enabled and run system tests:

cd packages/<package>
elastic-package stack up -v -d --version <kibana_constraint>
export ELASTIC_PACKAGE_FIELD_VALIDATION_TEST_METHOD=mappings
# Add defer-cleanup to check the data ingested in the corresponding indices/data streams
elastic-package test system -v --data-streams memory --defer-cleanup 900s

elastic-package stack down -v

Related issues

Screenshots

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: a6cf529

Failed CI Steps

• ✅ Check go sources

History

• 💚 Build #21790 succeeded e9a1f16
• 💚 Build #21673 succeeded e122783
• 💚 Build #21617 succeeded 959efee
• 💚 Build #21494 succeeded 1778899
• 💚 Build #21492 succeeded 8755628

cc @mrodm