I use never Oracle but OpenJDK from Liberia or from Azul. And now the question is: what do you want to do. Long term development? Then I would prefer in your place JDK 17 from Liberia, it is available as full JDK and as JRE where JRE is only the runtime environment.
Next question is: is it a tool for internal use or do you wand to use it for sale?
If it is only for internal use the clients should have installed the JRE at least or the JDK. The JRE is only around 50MB Download and comes also always as installable, binary package and also you can get it as Source Code.
If you want to develop with it for commercial sales I would prefer to build the platform packages what is really not that complex, with the command package you can build on the target platform the needed binary package which is a partial JRE and your Program as binary jar.
For internal use you would have to transfer only the jar File. Not complex also.
Java 17 is the latest its version of Java. The next its will come with Java 21 in September 23. I prefer to write and compile with the latest LTS which I can get security Updates until 2030. With switching to the next level of its JDK you may have small code fixings but - to speak truths - between Java 11 and Java 17 it wasn’t much to change.
So you can hold your binary building always on the last security update level and on it’s best bugfix level of compilers and runtimes included in Java OpenJDK Builds.
That is an LibreOffice Bug which was fixed already and has no relation to Java JDK or JRE but relations to a Bug in LibreOfice and OpenOffice while Apache OpenOffice was fixed in 2016 and Libre Office later in 2017. That has not to do with Java itself and could be done with setting a different path variable. So I don’t know what on this Bug we shall explain or looking on?