Update VS Code CodeLLDB references to LLDB DAP (#1055)

* Update VS Code CodeLLDB references to LLDB DAP

The extension now relies on LLDB DAP by default to integrate with the VS
Code debugger. Update references accordingly.

swiftlang/vscode-swift#1601

* Remove outdated configure LLDB note

Author: plemarquand

_posts/2022-07-14-vscode-extension.md

@@ -12,7 +12,7 @@ As Swift is deployed across more platforms, it is important that Swift can be de
 
 Swift is held back from extending outside the Apple ecosystem by the lack of a first-class, integrated development environment on non-Apple platforms. There is no Xcode if you are developing on Linux or Windows.
 
-Until this point there have been individual components to make up that development environment like Apple's [SourceKit-LSP](https://github.com/swiftlang/sourcekit-lsp) project and support for the Swift version of LLDB when using the [CodeLLDB](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb) extension, but nothing to bring them all together.
+Until this point there have been individual components to make up that development environment like Apple's [SourceKit-LSP](https://github.com/swiftlang/sourcekit-lsp) project and support for the Swift version of LLDB when using the [LLDB DAP](https://marketplace.visualstudio.com/items?itemName=llvm-vs-code-extensions.lldb-dap) extension, but nothing to bring them all together.
 
 The [Swift Server Workgroup](/sswg/) (SSWG) felt there was a need for a more complete solution. The Swift Extension for Visual Studio Code from the SSWG brings together many of these components into one package with everything pre-configured to work from the get-go.
 
@@ -38,7 +38,7 @@ The language server protocol (LSP) is a standard for providing language features
 
 ### Debugger
 
-A debugger is provided via the [CodeLLDB](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb) debugger extension. All the hard work integrating with LLDB is done by CodeLLDB. The Swift extension provides the integration with CodeLLDB by creating debug launch configurations for your project executables on start up. It also configures CodeLLDB to use the Swift version of LLDB.
+A debugger is provided via the [LLDB DAP](https://marketplace.visualstudio.com/items?itemName=llvm-vs-code-extensions.lldb-dap) debugger extension. All the hard work integrating with LLDB is done by the LLDB DAP (Debug Adapter Protocol) extension. The Swift extension provides the integration with LLDB DAP by creating debug launch configurations for your project executables on start up. It also configures LLDB DAP to use the Swift version of LLDB.
 
 ### Test Explorer
 

assets/images/getting-started-with-vscode-swift/debugging/configure-lldb.png

@@ -130,19 +130,9 @@ Visual Studio Code provides a rich debugging experience. See the
 more information.
 
 The Swift extension relies on the
-[Code-LLDB extension](https://github.com/vadimcn/vscode-lldb) to enable
+[LLDB DAP extension](https://marketplace.visualstudio.com/items?itemName=llvm-vs-code-extensions.lldb-dap) to enable
 debugging support.
 
-<div class="warning" markdown="1">
-The Swift extension will prompt you to configure settings for LLDB the first
-time you launch VS Code. You will need to either apply the configuration
-globally (user settings) or to your workspace (workspace settings) for the
-debugger to work properly.
-
-![Configure the Debugger](/assets/images/getting-started-with-vscode-swift/debugging/configure-lldb.png)
-
-</div>
-
 By default, the extension creates a launch configuration for each executable
 target in your Swift package. You may configure these yourself by adding a
 `launch.json` file to the root folder of your project. For example, this