New (currently failing) test for clashing direct and indirect dependencies

[hudlow]

Similar to #132, and possibly a regression introduced by #206.

The implementation "com.google.protobuf:protobuf-java:$protobufVersion" dependency causes Google's Protobuf Gradle plugin to place well-known-type protos in build/extracted-include-protos and the protobuf 'io.grpc:grpc-protobuf:1.75.0' dependency itself depends on the above protobuf-java package and thus causes Google's plugin to put the same well-known-type protos in the build/extracted-protos directory.

Then the Buf Gradle plugin adds both those directories as modules in its derived buf.yaml (build/bufbuild/buf.yaml) and the linter errors out over the ambiguity:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':bufLint'.
> Some Protobuf files had lint violations:
  src-main-proto/buf/test/v1/test.proto:19:8:google/protobuf/any.proto is contained in multiple modules:
    path: "build-extracted--include--protos-main"
    path: "build-extracted--protos-main"

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Dan Hudlow seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}