Updating JMXFetch to 0.47.5

[carlosroman]

What does this PR do?

This PR updates JMXFetch to 0.47.5 (previously 0.47.4).

Motivation

This version of JMXFetch just bumps the version of SnakeYAML to 2.0, DataDog/jmxfetch#413 as previous version had a CVE.

Additional Notes

N/A

Possible Drawbacks / Trade-offs

None.

Describe how to test/QA your changes

Either run an integration that uses JMXFetch (such as the Tomcat integration) or use the test server from here. Add the config example to your conf.d directory and check the Agent is reporting metrics back. Make sure to check that jmx.test.tabular_data_supp_foo is being sent correctly.

Reviewer's Checklist

• If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
• Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
• A release note has been added or the changelog/no-changelog label has been applied.
• Changed code has automated tests for its functionality.
• Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
• At least one team/.. label has been applied, indicating the team(s) that should QA this change.
• If applicable, docs team has been notified or an issue has been opened on the documentation repo.
• If applicable, the need-change/operator and need-change/helm labels have been applied.
• If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
• If applicable, the config template has been updated.

[estherk15]

Reviewed by docs team.