Standardize usage of virtual/override/final in apps/

Standardize usage of virtual/override/final in apps/

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=scheib@chromium.org

Committed: https://crrev.com/2f5be41e6ddc25cab9804910999255b539ecff1e
Cr-Commit-Position: refs/heads/master@{#300609}

[scheib, 2014-10-21 21:32:08]

The CQ bit was checked by scheib@chromium.org

[scheib, 2014-10-21 21:32:09]

lgtm

[commit-bot: I haz the power, 2014-10-21 21:33:57]

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

[commit-bot: I haz the power, 2014-10-22 01:46:16]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-10-22 04:05:06]

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