Standardize usage of virtual/override/final specifiers.

Standardize usage of virtual/override/final specifiers in chrome/browser/safe_browsing.

The Google C++ style guide states:

  Explicitly annotate overrides of virtual functions or virtual
  destructors with an override or (less frequently) final specifier.
  Older (pre-C++11) code will use the virtual keyword as an inferior
  alternative annotation. For clarity, use exactly one of override,
  final, or virtual when declaring an override.

To better conform to these guidelines, the following constructs have
been rewritten:

- if a base class has a virtual destructor, then:
    virtual ~Foo();                   ->  ~Foo() override;
- virtual void Foo() override;        ->  void Foo() override;
- virtual void Foo() override final;  ->  void Foo() final;

This patch was automatically generated. The clang plugin can generate
fixit hints, which are suggested edits when it is 100% sure it knows how
to fix a problem. The hints from the clang plugin were applied to the
source tree using the tool in https://codereview.chromium.org/598073004.

BUG=417463
R=noelutz@google.com

Committed: https://crrev.com/3456d92f5ba40d9fc3c5f6a1cd71c6d49a9dc7de
Cr-Commit-Position: refs/heads/master@{#301964}

[dcheng, 2014-10-29 17:45:48]

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

[dcheng, 2014-10-29 17:45:49]

+mattm, mind taking a look at this?

[mattm, 2014-10-29 21:00:59]

CL summary should add " in chrome/browser/safe_browsing."
otherwise lgtm.

[dcheng, 2014-10-29 21:02:28]

On 2014/10/29 at 21:00:59, mattm wrote:
> CL summary should add " in chrome/browser/safe_browsing."
> otherwise lgtm.

Done. I did that with a lot of my original changes, but it's a bit annoying to
do that and stay under 72 characters per line.

[dcheng, 2014-10-29 21:02:32]

The CQ bit was checked by dcheng@chromium.org

[commit-bot: I haz the power, 2014-10-29 21:04:51]

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

[commit-bot: I haz the power, 2014-10-29 21:11:48]

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

[commit-bot: I haz the power, 2014-10-29 21:11:50]

Try jobs failed on following builders:
  android_aosp on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_aosp/bu...)
  android_chromium_gn_compile_rel on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/android_chromiu...)
  chromium_presubmit on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)
  linux_chromium_asan_rel on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_compile_dbg_32 on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  win_chromium_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel/...)
  win_chromium_x64_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[dcheng, 2014-10-29 21:18:29]

The CQ bit was checked by dcheng@chromium.org

[commit-bot: I haz the power, 2014-10-29 21:20:18]

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

[commit-bot: I haz the power, 2014-10-29 23:01:42]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2014-10-29 23:02:22]

Patchset 2 (id:??) landed as
https://crrev.com/3456d92f5ba40d9fc3c5f6a1cd71c6d49a9dc7de
Cr-Commit-Position: refs/heads/master@{#301964}