Fixing target_bitrate_bps for a FullStackTest

Fixing target_bitrate_bps for a FullStackTest

While refactoring, I incorrectly set the target bitrate for one of the tests to
500k instead of 2000k.

This does not fix all the perf regressions.

BUG=chromium:534220
Committed: https://crrev.com/1356ba5e6ceb7513137b4052f0c2f9edddb11d5e
Cr-Commit-Position: refs/heads/master@{#10008}

[ivica, 2015-09-21 15:59:58]

The CQ bit was checked by ivica@webrtc.org to run a CQ dry run

[commit-bot: I haz the power, 2015-09-21 16:00:04]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1356123002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1356123002/1

[ivica, 2015-09-21 16:00:45]

ivica@webrtc.org changed reviewers:
+ pbos@webrtc.org

[pbos-webrtc, 2015-09-21 16:06:28]

lgtm

[commit-bot: I haz the power, 2015-09-21 18:00:20]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-09-21 18:00:20]

Dry run: Try jobs failed on following builders:
  android on tryserver.webrtc (JOB_TIMED_OUT, no build URL)
  android_rel on tryserver.webrtc (JOB_TIMED_OUT, no build URL)

[ivica, 2015-09-22 07:36:36]

The CQ bit was checked by ivica@webrtc.org

[commit-bot: I haz the power, 2015-09-22 07:36:48]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1356123002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1356123002/1

[commit-bot: I haz the power, 2015-09-22 08:09:15]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-09-22 08:09:27]

Patchset 1 (id:??) landed as
https://crrev.com/1356ba5e6ceb7513137b4052f0c2f9edddb11d5e
Cr-Commit-Position: refs/heads/master@{#10008}