fix(docs): remove misleading debugger instructions

It should help to avoid issues like this:
#404 (comment)

Author: sidlatau

README.md

@@ -441,10 +441,6 @@ This plugin integrates with [nvim-dap](https://github.com/mfussenegger/nvim-dap)
 Currently if `debugger.enabled` is set to `true` in the user's config **it will expect `nvim-dap` to be installed**.
 If `dap` is this plugin will use `flutter` or `dart` native debugger to debug your project.
 
-To use the debugger you need to run `:lua require('dap').continue()<CR>`. This will start your app. You should then be able
-to use `dap` commands to begin to debug it. For more information on how to use `nvim-dap` please read the project's README
-or see `:h dap`. Note that running the app this way will prevent commands such as `:FlutterRestart`, `:FlutterReload` from working.
-
 You can use the `debugger.register_configurations` to register custom runner configuration (for example for different targets or flavor).
 If your flutter repo contains launch configurations in `.vscode/launch.json` you can use them via this config :
 

doc/flutter-tools.txt

@@ -499,12 +499,6 @@ to provide debug capabilities. Currently if `debugger.enabled` is set to `true`
 in the user’s config **it will expect nvim-dap to be installed**. If `dap` is
 this plugin will use `flutter` or `dart` native debugger to debug your project.
 
-To use the debugger you need to run `:lua require('dap').continue()<CR>`. This
-will start your app. You should then be able to use `dap` commands to begin to
-debug it. For more information on how to use `nvim-dap` please read the
-project’s README or see |dap|. Note that running the app this way will
-prevent commands such as `:FlutterRestart`, `:FlutterReload` from working.
-
 You can use the `debugger.register_configurations` to register custom runner
 configuration (for example for different targets or flavor). If your flutter
 repo contains launch configurations in `.vscode/launch.json` you can use them