Issue Type: Bug

A recent update changed the behavior of workbench.action.findInFiles in an extremely undesirable way for me. Like, constant source of frustration throughout my day kind of way.

Previously, triggering search would open the panel and seed the search box with any text I had selected, but it wouldn't actually run the search. Since I think 1.40 or 1.41 invoking workbench.action.findInFiles both seeds the search text and begins an actual search. This happens despite setting "search.searchOnType": false. The only way I've found to stop this auto-search behavior is to set "editor.find.seedSearchStringFromSelection": false, but that's an undesirable workaround.

The reason this is such a big issue for me is that it ends up constantly re-running the search. In the large codebase I work in most often this takes about 2 seconds and ends up happening after every search result I look at.

My workflow looks like this:

• Invoke workbench.action.findInFiles to begin a search
• Type some text and hit enter
• Select a result and press enter
• Look at the opened editor
• Invoke workbench.action.findInFiles to return focus to search
• Select a different result and press enter
• repeat

The problem is with return focus to search. Since selecting a search result opens an editor with the matching text selected then if I don't clear the selection before invoking workbench.action.findInFiles is starts a brand new search. This means I have to wait for the search to complete, and worse, it blows up the tree view where I had collapsed some files that I'd finished inspecting.

VS Code version: Code 1.41.1 (26076a4, 2019-12-18T14:58:56.166Z)
OS version: Windows_NT x64 10.0.17763