dap-view configuration at adapter config level

[catgoose]

Instead of creating config keys for different adapters and since you can get an adapter's config from dap.session(), you could instruct the user to create dap_view config key in their adapter config:

    dap.configurations.go = {
      {
        type = "go",
        name = "Debug main.go",
        request = "launch",
        showLog = true,
        program = "${workspaceFolder}/main.go",
        dlvToolPath = dlvToolPath,
        dap_view = {
          terminal = {
            enabled = false,
          },
        },
      },
}

Then you don't have to update dap-view setup opts, only create the logic in the plugin and update readme about what dap_view.

This also allows the user to have finer grain control over dap-view. For example if I have two delve configurations, one that is for a web application and the other TUI:

    dap.configurations.go = {
      {
        type = "go",
        name = "Debug main.go Webserver",
        request = "launch",
        showLog = true,
        program = "${workspaceFolder}/main.go",
        dlvToolPath = dlvToolPath,
        dap_view = {
          terminal = {
            enabled = false,
          },
        },
      },
      {
        type = "go",
        name = "Debug main.go TUI",
        request = "launch",
        showLog = true,
        program = "${workspaceFolder}/main.go",
        dlvToolPath = dlvToolPath,
        dap_view = {
          terminal = {
            enabled = true,
          },
        },
      },
}

I'm sure we could provide callbacks in the adapter configuration as well.

Personally I like this sort of inversion pattern because it requires the least amount of complexity at the plugin level and provides the user with the most flexibility.