Use SharedMemoryHandle instead ScopedHandle as ivar for SharedMemory

Only Windows was using ScopedHandle. Other platforms already used a
SharedMemoryHandle directly. The theoretical benefit of ScopedHandle is that it
correctly deals with ownership. But all that does is ensure that the handle is
closed during destruction of SharedMemory, which is already explicitly coded,
since it's needed on all platforms. Switching to SharedMemoryHandle is needed to
correctly propagate other state on SharedMemoryHandle, which is being added in
the near future.

BUG=713763

Review-Url: https://codereview.chromium.org/2854833004
Cr-Commit-Position: refs/heads/master@{#469179}
5 files changed