Improve debugger README
Clarification and motivation
As we are preparing our debugger to be published, we should make its README matter, there are some obvious problems with it.
Acceptance criteria
- Currently when you open https://gitlab.com/morley-framework/morley/-/tree/master/code/morley-debugger from the root README, you only see mentions of the console debugger. We should make it easy to notice that we also have VSCode debugger.
- I think we should list features of the debugger. And perhaps provide a list of the most essential features we will have later. For example, see how it's done for LIGO plugin: https://marketplace.visualstudio.com/items?itemName=ligolang-publish.ligo-vscode. Currently we say "This README describes how to obtain and install the extension", but installation instruction should be only part of README, we should also describe what this tool (debugger) can do and maybe provide some usage tips (if there are any).