Handling `boringssl` vs. `openssl` in the module graph

We are facing ODR violations for `boringssl` vs `openssl`.

Some of our (transitive) dependencies depend on the former while others depend on the latter and this causes linker issues when both are used within some dependency closure.

How is this supposed to be solved in the Bazel ecosystem?

Start by tracing Bazel's module graph handling for transitive dependencies that bring in boringssl and openssl, then examine how the resulting dependency closure reaches the linker. Reproduce the reported ODR violation and determine what Bazel behavior or guidance would prevent both libraries from conflicting; the issue is done when that resolution is implemented or clearly documented.

Written by the indexing model from the issue text.