Readme improvements

[dansomething]

• Add note regarding possible slow startup times. Can't view source code #20
• Illustrate roughly how it works. Could not get debugger to work #3
• Link to a full working example
• Possibly update "adapters" config? Update the README for setting the "adapters" config #14
• Add note regarding no multi-session support. Multiple Vimspector debugging sessions at the same time? #16
• Improve profiles documentation? Multiple configurations at the same time? #7
• Add note regarding hot code replacement. Hot code replace? #9 Is hot-swap code possible? #31

[Konfekt]

Hello, thank you for creating this plug-in the quest for a debugging experience as convenient as IntelliJ's. I did not fully get to what extent this depends on Coc (in view of newer alternatives like lsp)?

[dansomething]

Hello, thank you for creating this plug-in the quest for a debugging experience as convenient as IntelliJ's. I did not fully get to what extent this depends on Coc (in view of newer alternatives like lsp)?

This plugin uses Coc for convenience when interacting with the Java language server and for creating a simple user interface. For example, it is used to execute LSP commands. This could be done with any LSP integration for Vim/Nvim, but it's very easy with Coc. There's also the main method selection user interface. That could be implemented in other ways, but Coc also makes it so easy. This whole plugin is intended to be the simplest solution to glue the pieces together. See Readme#Goals