Embedding arbitrary web content is problematic when it comes to keyboard shortcuts because:
- Web content can steal app shortcuts (see e.g. brave/browser-laptop#4407)
- Blocked web content (e.g. a focused `<webview>` performing expensive computation) will also prevent app shortcuts from firing immediately

To fix this, we need a way to _always_ handle certain shortcuts in the main process. I think the most flexible solution would be something like this:

``` js
app.addProtectedShortcut('CmdOrCtrl+Tab', (event) => {
  event.preventDefault();
});
```

We could then implement:

``` cpp
bool CommonWebContentsDelegate::PreHandleKeyboardEvent(
    content::WebContents* source,
    const content::NativeWebKeyboardEvent& event,
    bool* is_keyboard_shortcut) {
  return /* event is protected shortcut and the handler called preventDefault */;
}
```

@zcbenz Thoughts? I'm happy to work on this if we come up with a reasonable approach.

atom/browser/api/atom_api_web_contents.cc
if (embedder) {
    NativeWindow* owner_window = nullptr;
    auto relay = NativeWindowRelay::FromWebContents(embedder->web_contents());
    if (relay) {
      owner_window = relay->window.get();
    }
    if (owner_window)
      SetOwnerWindow(owner_window);
    content::RenderWidgetHostView* rwhv =
        web_contents()->GetRenderWidgetHostView();
    if (rwhv) {
      rwhv->Hide();
      rwhv->Show();
    }
  }
}
v8::Local<v8::Value> WebContents::DevToolsWebContents(v8::Isolate* isolate) {
  if (devtools_web_contents_.IsEmpty())
    return v8::Null(isolate);
  else
    return v8::Local<v8::Value>::New(isolate, devtools_web_contents_);
}
v8::Local<v8::Value> WebContents::Debugger(v8::Isolate* isolate) {
  if (debugger_.IsEmpty()) {
    auto handle = atom::api::Debugger::Create(isolate, web_contents());
    debugger_.Reset(isolate, handle.ToV8());
  }
  return v8::Local<v8::Value>::New(isolate, debugger_);
}
void WebContents::BuildPrototype(v8::Isolate* isolate,