Update HTTPHeaderMap wrappers to use AtomicString type for header values

Update HTTPHeaderMap wrappers to use AtomicString type for header values

Update HTTPHeaderMap wrappers to use AtomicString type for header values instead
of String, for consistency with HTTPHeaderMap. This avoids uselessly constructing
Strings and then having to convert it to an AtomicString, which has a cost.

A lot of callers already have an AtomicString or a string literal, so we end up
constructing AtomicStrings from Strings a lot less.

HTTPHeaderMap uses AtomicString type for both header names and values to save
memory, as there are a lot of identical strings.

R=abarth, eseidel
BUG=323739
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=163027

[eseidel, 2013-12-02 18:47:58]

lgtm

[commit-bot: I haz the power, 2013-12-02 19:40:49]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/ch.dumez@samsung.com/99733002/20001

[commit-bot: I haz the power, 2013-12-02 20:40:45]

Change committed as 163027