Remove dev_dependency from buildifier_prebuilt.

[criemen]

Otherwise, including any targets from //:BUILD.bazel in something that gets invoked from the internal build system will result in a missing dependency error.
This is relevant for C#, where I add a file export to LICENSE to the top-level BUILD.bazel file.

[redsun82]

Annoying, but then I would rather put the buildifier target elsewhere where it doesn't cause such problems, rather than making the internal repo pull it in. Maybe if the buildifier target is moved into misc/bazel/BUILD.bazel it should be ok?

[criemen]

That'd work, too! Does it still work if it's not placed in the top-level folder? I wasn't sure about this.

We also should/could duplicate the buildifier setup internally anyways, then we'd not "just" pull in this module for the external repo - after all, it's rather useful.

[redsun82]

That'd work, too! Does it still work if it's not placed in the top-level folder? I wasn't sure about this.

It works, yes 🙂

We also should/could duplicate the buildifier setup internally anyways, then we'd not "just" pull in this module for the external repo - after all, it's rather useful.

In any case we'd need to add another explicit bazel_dep, as we can't use a module pulled in transitively. But it's true that then the dev dependency wouldn't be that useful.

[criemen]

Closing in favor of #16435.

Yeah the second point was what I was thinking. Anyways, let's go with your solution for now!