Deprecate GuavaComponentRule #251
Description
We have this in the test that looks for Gradle 7.6.4 and only then runs with the full set of versions, but in the Gradle build, we don't set up a cross version test group with this version. I think what we want to do is activate this code path when we're running with the latest Gradle version. This has to be dynamic in the sense that we don't need to update the condition each time a new Gradle release comes out.
After reviewing the code, we realized that the GuavaComponentRule that is tested here, is quite opinionated (because it removes dependencies without giving control over what is removed), and doesn't work for the latest Guava releases. We've decided to deprecate the rule and document how to achieve the same thing using the patch DSL.