So for shops that are already open to using the JDK they're obviously already used to the legalese/implications for companies built on this software.

Everyone else in the world probably does not see this as "straight forward".

So Step 0, be a lawyer.

Oracle has specifically reworked its license to make terms clear after the bad press around the initial release of Oracle JDK 17:

https://blogs.oracle.com/java/post/free-java-license

Any company using Java should be willing to read and understand Oracle's terms, whether they use third party OpenJDK distributions or Oracle's builds.

If you're leaving significant performance gains on the table because you can't read, that's on you.

Just like most FOSS licenses, that in big corps always got through legal.

In the projects where that isn't required, usually we have licence validation tooling on the CI/CD pipeline, that breaks the build if the legal wishes aren't fulfilled.