Fix unused qualifications in runfiles

[palfrey]

Fixes https://github.com/bazelbuild/rules_rust/issues/3493

[google-cla[bot]]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[palfrey]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Fixed

[palfrey]

Thanks! Just one question.

What's the question?

[dzbarsky]

I'm not sure we want to sign up to maintain arbitrary style choices for people who depend on rules_rust... How does this code end up triggering these problems for you? As far as I'm aware, both Bazel and Cargo apply different lint expectations to your own code vs your dependencies...

rules_rust emits --cap-lints=allow for all crate_universe deps (third-party) but the runfiles lib is not one of those. From bazel's POV it's a "first-party" target even though it comes from an external repo. And this repo never sets the flag on the rust_library, so tweaking that would be another way to fix this.

Whichever way we move forward with, I would have hoped that a PR doing a bit of warning cleanup/hygiene would not become so contentious.