Update BrowserAccessibilityManager to support Lollipop SDK.

Update BrowserAccessibilityManager to support Lollipop SDK.

Renames KitKatBrowserAccessibilityManager to LollipopBrowserAccessibilityManager
because we were never able to use the KitKat variant due to KitKat framework
bugs.

Adds a new method specifically for adding actions to AccessibilityNodeInfo,
so we can use the new API in Lollipop, and suppresses the deprecation warnings
in the non-Lollipop implementation.

This gets rid of all of the remaining deprecation warnings in content/.

BUG=405174
Committed: https://crrev.com/9ce3a2076eb4b295e9d9d4aa0660c0a8bb103242
Cr-Commit-Position: refs/heads/master@{#316293}

[dmazzoni, 2015-02-13 18:43:11]

dmazzoni@chromium.org changed reviewers:
+ aurimas@chromium.org, plundblad@chromium.org

[newt (away), 2015-02-13 18:48:08]

newt@chromium.org changed reviewers:
+ newt@chromium.org

[newt (away), 2015-02-13 18:48:08]

drive-by woohoo!

Thanks for cleaning this up :)

[aurimas (slooooooooow), 2015-02-13 18:56:57]

lgtm

[dmazzoni, 2015-02-13 20:01:47]

The CQ bit was checked by dmazzoni@chromium.org

[commit-bot: I haz the power, 2015-02-13 20:02:32]

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

[aurimas (slooooooooow), 2015-02-13 20:04:03]

aurimas@chromium.org changed reviewers:
+ dtrainor@chromium.org

[aurimas (slooooooooow), 2015-02-13 20:04:04]

You need an LGTM for an OWNER. +dtrainor

[commit-bot: I haz the power, 2015-02-13 21:33:26]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-13 21:34:05]

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