<!--  As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->

### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->

* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

### Issue Details

* **Electron Version:**
  * 8.5.0
* **Operating System:**
  * macOS 10.15.5
* **Last Known Working Electron version:**
  * none

### Expected Behavior
<!-- A clear and concise description of what you expected to happen. -->
After `click` on the notification that is in the reply mode one of the following should apply:
- don't destroy notification and provide additional property with `event`, that includes information if notification is in the reply mode or not.
- close notification completely (remove it from the screen)

### Actual Behavior
<!-- A clear and concise description of what actually happened. -->
Clicking on notification when in reply "mode", doesn't remove notification from the screen, but all the listeners are destroyed.

### To Reproduce
<!--
Your best chance of getting this bug looked at quickly is to provide an example.
-->
Issues is reproducible with `NSUserNotificationAlertStyle` set to `alert` or `banner`

Main Process:
```ts
let notification;
app.on('ready', () => {
  notification = new Notification({
    title: 'Title',
    body: 'Notification body',
    hasReply: true,
  });
  notification.on('reply', (ev, reply) => {
    console.log('Reply: ', reply);
  });
  notification.show();
});
```

1. When notification appears click on the `reply` button.
2. Start typing text
3. Click on the notification body
4. Click `reply` to send text from input

Result:
`reply` callback is not executed.
Nothing appears in the console.

### Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->
Notification in reply mode (waiting for input):
<img width="358" alt="Screenshot 2020-08-20 at 14 29 33" src="https://user-images.githubusercontent.com/27143015/90770210-b9c65500-e2f1-11ea-98c9-111fbb74a0a1.png">

### Additional Information
<!-- Add any other context about the problem here. -->

shell/browser/notifications/win/windows_toast_notification.cc
ABI::Windows::UI::Notifications::IToastNotification* toast) {
  if (FAILED(toast->remove_Activated(activated_token_)))
    return false;
  if (FAILED(toast->remove_Dismissed(dismissed_token_)))
    return false;
  return SUCCEEDED(toast->remove_Failed(failed_token_));
}
/*
/ Toast Event Handler
*/
ToastEventHandler::ToastEventHandler(Notification* notification)
    : notification_(notification->GetWeakPtr()) {}
ToastEventHandler::~ToastEventHandler() {}
IFACEMETHODIMP ToastEventHandler::Invoke(
    ABI::Windows::UI::Notifications::IToastNotification* sender,
    IInspectable* args) {
  base::PostTask(
      FROM_HERE, {content::BrowserThread::UI},
      base::BindOnce(&Notification::NotificationClicked, notification_));
  if (IsDebuggingNotifications())
    LOG(INFO) << "Notification clicked";
  return S_OK;
}
IFACEMETHODIMP ToastEventHandler::Invoke(