Describe the bug
From what I understand, guava 30 is purposefully being shadowed and relocated into graphql-java. This seems to be reflected properly in the graphql-java pom, which properly does not have a guava dependency. Unfortunately, it is not reflected in the gradle library metadata, where the guava dependency is still present: https://repo1.maven.org/maven2/com/graphql-java/graphql-java/17.3/graphql-java-17.3.module

This means that maven consumers properly do not receive guava 30 through graphql-java, but gradle consumers improperly do receive the gradle 30 dependency.