HADOOP-19878. Upgrade to Netty 4.1.113.Final due to CVEs

[pjfanning]

Description of PR

https://issues.apache.org/jira/browse/HADOOP-19878

How was this patch tested?

For code changes:

• Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
• Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
• If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

AI Tooling

If an AI tool was used:

• The PR includes the phrase "Contains content generated by "
  where is the name of the AI tool used.
• My use of AI contributions follows the ASF legal policy
  https://www.apache.org/legal/generative-tooling.html

[steveloughran]

+1 pending the build.

@pjfanning we really an upgrade marathon don't we, where everything which can be upgraded is (trunk, and 3.5) and anything which still works on java8 is done for the 3.4 branch. Then we can think of new releases

[ajfabbri]

+1 pending jenkins/pr-merge CI passing. We can ignore the PR update / Build (pull_request_target) — Workflow run detection failed check for now: We are adding new github actions-based CI which requires enabling actions in your forked repo to get past that error, but it is not a requirement yet.

[pan3793]

are all those netty libs used by hadoop? I don't think hadoop requires netty-codec-redis ...

[pjfanning]

it feels like there is a separate task to revisit the entire LICENSE-binary file - I guarantee that this is not the only is it/isn't it correct line in the file