Cleanup test exclusion configs for remoting_unittests.

Many of the remoting_unittests that were excluded for TSan do not
exist anymore or were renamed. Tests that do exist should pass now.

BUG=110729,132164

Review URL: https://chromiumcodereview.appspot.com/10855008

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150196 0039d316-1c4b-4281-b951-d872f2087c98

tools/valgrind/gtest_exclude/remoting_unittests.gtest-tsan.txt

-# Following tests create real libjingle connections, and libjingle has
-# hardcoded timeouts, so these tests fail under TSan.
-JingleSessionTest.Connect
-JingleSessionTest.ConnectBadChannelAuth
-JingleSessionTest.TestUdpChannel
-JingleSessionTest.TestTcpChannel
-JingleSessionTest.TestSpeed

tools/valgrind/gtest_exclude/remoting_unittests.gtest-tsan_win32.txt

-# These test use google_breakpad::CrashGenerationServer that seems to have race
-# conditions. See http://crbug.com/132164
-BreakpadWinDeathTest.TestAccessViolation
-BreakpadWinDeathTest.TestInvalidParameter
-BreakpadWinDeathTest.TestDebugbreak
-
-# Following tests create real libjingle connections, and libjingle has
-# hardcoded timeouts, so these tests fail under TSan.
-JingleSessionTest.Connect
-JingleSessionTest.TestUdpChannel
-JingleSessionTest.TestTcpChannel
-JingleSessionTest.TestSpeed

tools/valgrind/gtest_exclude/remoting_unittests.gtest.txt

-# Flaky and sometimes hangs under Valgrind, see http://crbug.com/103774
-JingleSessionTest.TestSpeed