Remove ListValue::Append(new {Fundamental,String}Value(...)) usage in //chrome (part 2)

Remove ListValue::Append(new {Fundamental,String}Value(...)) usage in //chrome (part 2)

The raw pointer overload of ListValue::Append() is deprecated and will
be removed. Instead, code should just write:
- ListValue::AppendBoolean()
- ListValue::AppendInteger()
- ListValue::AppendDouble()
- ListValue::AppendString()

This wasn't included in the original CL because the clang tool got
confused when processing this file. It turns out true and false can be
macros!

BUG=581865
Committed: https://crrev.com/930694e095e2f25add4d39d5478a952b481332a3
Cr-Commit-Position: refs/heads/master@{#397858}

[dcheng, 2016-06-03 21:30:30]

dcheng@chromium.org changed reviewers:
+ xiyuan@chromium.org

[xiyuan, 2016-06-03 21:34:40]

lgtm

[dcheng, 2016-06-03 21:36:50]

The CQ bit was checked by dcheng@chromium.org

[commit-bot: I haz the power, 2016-06-03 21:37:20]

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

[commit-bot: I haz the power, 2016-06-04 00:41:55]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-04 00:43:44]

Description was changed from

==========
Remove ListValue::Append(new {Fundamental,String}Value(...)) usage in //chrome
(part 2)

The raw pointer overload of ListValue::Append() is deprecated and will
be removed. Instead, code should just write:
- ListValue::AppendBoolean()
- ListValue::AppendInteger()
- ListValue::AppendDouble()
- ListValue::AppendString()

This wasn't included in the original CL because the clang tool got
confused when processing this file. It turns out true and false can be
macros!

BUG=581865
==========

to

==========
Remove ListValue::Append(new {Fundamental,String}Value(...)) usage in //chrome
(part 2)

The raw pointer overload of ListValue::Append() is deprecated and will
be removed. Instead, code should just write:
- ListValue::AppendBoolean()
- ListValue::AppendInteger()
- ListValue::AppendDouble()
- ListValue::AppendString()

This wasn't included in the original CL because the clang tool got
confused when processing this file. It turns out true and false can be
macros!

BUG=581865

Committed: https://crrev.com/930694e095e2f25add4d39d5478a952b481332a3
Cr-Commit-Position: refs/heads/master@{#397858}
==========

[commit-bot: I haz the power, 2016-06-04 00:43:45]

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