We've finally found and understood the issue.  It was down to a configuration on the SQL Server to use dynamic ports, but then define the port to listen on buried in the network configuration.  Once we had the right port to talk on, the JDBC connection was accepted and is working (very similar code to what you shared).

Thanks for your help!  Let's hope Lakehouse Federation will work with this configuration too!