Switching between input modes via the "Set input mode UI only" node and the "Set input mode Game and UI" node consumes all input for editor

When Changing the between input modes with the "Set input mode UI only" node and the "Set input mode Game and UI" node the editor can become unresponsive. The user can still click on things but it will have no effect. For example. The user can not stop PIE or navigate the content browser window or pause the game.

1. Open Editor
2. Create a New Widget Blueprint
   Right Click the content browser > User Interface > Widget Blueprint
3. Open New widget blueprint
4. Add a button to the designer graph
5. Add an "OnClicked" event
   Select the button > Scroll to the bottom of the details panel > add on clicked event
6. Go to the event graph of the widget blueprint
7. Create the blueprint in the attached image
8. Compile and save
9. Open level blueprint
10. Add the widget to the viewport
    Event begin play > Create widget > select your new widget blueprint that was just made > add to viewport
11. Compile and save
12. Click Play in Editor
13. Press the 'K' key
14. Click the button on screen
15. Press the 'K' key again
16. Notice that the print string is now only returning "True" even thought key was released
17. Notice that the stop PIE button in no longer responding (along almost all other Editor buttons)

Bug: Mouse Clicks not responding after set Input UI, then to Game

Bug: Mouse Clicks not responding after set Input UI, then to Game

After using Set Input, Mouse Clicks unresponsive

Bug: Mouse Clicks not responding after set Input UI, then to Game