[AWS][EMR] Update metric type and set dimensions fields

[constanca-m]

What does this PR do?

The data stream already had the metric type defined for the metric fields. However, they were not according to TSDB baselines and they had the same problem as described in #6952:

All metric fields are calculated through an aggregation (sum or avg). However, this is only for a given timestamp. On the next timestamp, new values will be used on the final aggregation and so on.

Because of this, the value for some field, 4XXError.sum for example, does not relate to the next 4XXError.sum field. The values are not cumulative over the different timestamps, and that is a requirement for a counter field.

All metric fields are gauge in this data stream.

The ECS dimension fields chosen in #5193 (comment) were set.

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

Relates to #6293.

[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-07-14T13:17:21.019+0000

• Duration: 54 min 9 sec

Test stats 🧪

Test	Results
Failed	0
Passed	194
Skipped	4
Total	198

🤖 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% (15/15)	💚
Files	93.75% (15/16)	👎 -6.25
Classes	93.75% (15/16)	👎 -6.25
Methods	85.714% (240/280)	👎 -2.238
Lines	85.925% (7387/8597)	👎 -4.884
Conditionals	100.0% (0/0)	💚

[elasticmachine]

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