Maintenance Request: Add label to issues of build errors when compiling crates

[UebelAndre]

To better track and understand issues around various build errors in dependencies generated by cargo raze, could a label be added to related issues to better group and identify them? I think this would make it easier for users to find similar issues that might already have a workaround.

In the mean time, I did a quick pass over existing issues and came up with the following list:

• Tracking crates with exotic build.rs #41
• compiling terminfo #64
• Log 0.4.8 and 0.3.9 generation issue --cfg=atomic_cas #110
• Cannot build project with reqwest library #113
• unable to compile syn #159
• Support Request: Building wasm-pack #194

This appears to be the largest (and also likely the hardest to solve) issue for this project. I really feel if a solution could be found, it'd be huge for both the Bazel and Rust communities ❤️

[UebelAndre]

@damienmg Not sure if this is the best place to mention this but in regards to rust-lang/cargo#7614. What is currently missing from manifest that would solve for the issues seen above? I thought --build-plan gave a more accurate set of features being used in what dependencies and the information gathered from the output could lead to a solution.