Add drop into editor API

[mjbvz]

Exploration of dragging a file from VS Code's explorer into an editor to create a link. Example use case would be dragging a file into a markdown editor to insert a link

[mjbvz]

I have a prototype but need to think more about what the design should look like. Biggest question I have right now:

Should we allow there to be multiple of these drop handlers active at one time? We do want to allow there to be multiple drop handlers where each one handles a different dropped mime type, but what about multiple handlers for a single mime type? In markdown for example, you can imagine having one drop handler that creates links and another that creates image links

If we did allow this, presumably we then need some way for the user to control what happens on drop, either with a setting to configure the default or by presenting a list of actions to them

---

Answering this helps determines if we go with more of a provider style api or more of an event api

[mjbvz]

@misolori @sbatten I've added some basic prompt text to the drop overlay:

Untitled.mov

This text only shows up when you are dropping into the whole editor. It hides itself if the drop is previewing a split (however holding down shift still lets you enter "drop into editor" mode)

Let me know what you think about this behavior. I also think we need to make the Hold shift to drop into editor text more prominent, potentially by adding a solid background to it. Would appreciate some design help and suggestions on this

[sbatten]

Yea the visual presentation of the text is my main call for improvement. Both in terms of prominence and using the key presentation we have in the command palette