First prove that spring-devtools isn't compatible with constraints.drl

Read this comment:
https://stackoverflow.com/questions/61371336/optaplanner-solvermanager-bean-not-being-found-in-spring-application/61522211?noredirect=1#comment110010877_61522211

It's in the docs, but docs are there to explain new features. Documenting pitfalls is less helpful than detecting them during coding.

Requirements:
In the spring boot starter, if the SolverConfig constains scoreDRL or scoreDRLFile (regardless if it was build automatically or if there is an actual xml file that declares those), AND if spring-devtools is in the classpath (do this without adding a dependency on it. A typical trick is Class.forName() throws or doesn't throw an Exception, but StackOverflow it for a more modern approach), then a log.warn("...") that devtools isn't compatible with it.