[mergify]

The Netty frame handler factory was created on the first connection and cached for the lifetime of the connection factory. Any later change to the Netty configuration (TLS context, event loop group, customizers, enqueuing timeout) or to the connection timeout, socket configurator, and recovery settings was silently ignored for new connections. This is inconsistent with the blocking IO transport.

The Netty frame handler factory is now created for each connection, like the blocking IO one. Existing connections, including their recovery, keep using the factory they were created with.

ConnectionFactory#clone() also shared the Netty configuration with the original factory. The clone now gets its own copy.

---

This is an automatic backport of pull request #2133 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 8e3ac43 has failed:

On branch mergify/bp/v5.x/pr-2133
Your branch is up to date with 'origin/v5.x'.

You are currently cherry-picking commit 8e3ac43.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   src/main/java/com/rabbitmq/client/ConnectionFactory.java
	both modified:   src/test/java/com/rabbitmq/client/test/ConnectionFactoryTest.java

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally