Instrumented libraries: use package-specific sanitizer blacklists.

Instrumented libraries: use package-specific sanitizer blacklists.

Previously we used a single blacklist file per sanitizer. The same file was used
for Chromium and for every instrumented package. This change allows choosing a
different blacklist file for each package, which means that package targets may
now depend on the blacklist files, avoiding expensive clobbers.

This CL also blacklists two known issues in instrumented libraries.

BUG=313751, 367509
R=glider@chromium.org
NOTRY=true
TEST=MSan interactive_ui_tests, ASan compile

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=282959

[Alexander Potapenko, 2014-07-14 16:24:40]

lgtm

[earthdok, 2014-07-14 16:25:15]

The CQ bit was checked by earthdok@chromium.org

[commit-bot: I haz the power, 2014-07-14 16:26:19]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/earthdok@chromium.org/390093002/20001

[commit-bot: I haz the power, 2014-07-14 16:27:31]

Change committed as 282959