The camel-smb component does not recover properly after SMB server has network issue / resets connection

• After a connection reset happens, the connection is never re-created and subsequent calls give a broken pipe exception
• We tried to fix this with disconnect=true so connections are re-created more frequently but due to some unnecesary connection-leases tracking the smbj library thinks there are still leases outstanding and won't close the connection, and causes the SMB server to send a connection reset because of that as all sessions are closed gone but the connection remains.

This PRs would need to be back ported to 4.10.x to fix the issue:

• https://github.com/apache/camel/pull/18892
• https://github.com/apache/camel/pull/18387
• https://github.com/apache/camel/pull/18397
• https://github.com/apache/camel/pull/18399
• https://github.com/apache/camel/pull/18507