Fix native image build when using Netty

[dagnir]

Motivation and Context

NettyNioAsyncHttpClient does not work in GraalVM native images. Requests fail with:

  Caused by: java.util.concurrent.TimeoutException: Acquire operation took longer than 10000 milliseconds.
  	at software.amazon.awssdk.http.nio.netty.internal.HealthCheckedChannelPool.timeoutAcquire(HealthCheckedChannelPool.java:77)

Pooled ByteBuf allocation fails with

  NoClassDefFoundError: Could not initialize class
  io.netty.util.internal.shaded.org.jctools.queues.unpadded.MpscUnpaddedArrayQueue

Exposed by #6968 (released in 2.44.10), which removed the UnpooledByteBufAllocator
workaround for JDK SSL pipelines. That workaround kept TLS pipelines off the pooled
allocator, masking the incompatibility.

Modifications

• Add --initialize-at-build-time=io.netty.util.internal.shaded.org.jctools to
  netty-nio-client's native-image.properties.

Testing

Verified by building a native-image application using S3 w/ Netty and making a test service call.

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[github-actions]

This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one.