[backport] [7.43.x] Upgrade JMXFetch to 0.47.6

[scottopell]

What does this PR do?

Backport of #16364

Motivation

See above PR

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

• Run a java app with JMX metrics exposed (eg, Tomcat, activemq, solr)
• Configure agent to collect jmx metrics
• Ensure the JMX metrics are visible in the app

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.

[drichards-87]

Left you one small piece of feedback from Docs. PR is approved.

[scottopell]

Back to draft until DataDog/jmxfetch#420 and DataDog/jmxfetch#419 land and we release a new jmxfetch version that we can reference here.