Upgrade netty to resolve CVEs

[zkirksey]

What does this PR do?

Upgrade netty to 4.1.133.Final to resolve CVEs

Who is reviewing it?

(please choose AT LEAST two reviewers that need to approve the PR before it can get merged; if a component team is listed, at least one of its members needs to approve)

Choose 2 committers to review/merge the PR.

(please choose ONLY two committers from below, delete the rest)

@andrewkfiedler
@bdeining
@beyelerb
@brendan-hofmann
@brjeter
@clockard
@coyotesqrl
@figliold
@jaymcnallie
@jlcsmith
@kcwire
@lessarderic
@michaelmenousek
@millerw8
@mrmateo
@pklinef
@ricklarsen - Documentation
@rzwiefel
@shaundmorris
@stustison
@tbatie
@vinamartin

How should this be tested?

Any background context you want to provide?

What are the relevant tickets?

CAL-xxx

Screenshots (if appropriate)

Checklist:

• Documentation Updated
• Update / Add Threat Dragon models
• Update / Add Unit Tests
• Update / Add Integration Tests

[jaymcnallie]

Somewhere along the way netty-all changed from a fat bundle to an aggregator. It builds fine if you include netty-all since the build will resolve all the transitive dependencies. However, loading just netty-all into the OSGi container doesn't actually bring the submodules onto the class path at runtime. Update to explicitly depend on the submodules required. The sdk-app features file will need to be updated too.