Build-based SDK and toolchain management

In this release, the extension transitioned from the extension-wide SDK and toolchain management to using SDK and toolchain management for each build configuration. This change affects most areas of the nRF Connect extension. Entries directly related to this change are gathered below:

• Applications

  • Restricted the SDK version choice for workspace and repository applications.

• Workspaces

  • Removed the restriction of having only one west workspace or SDK in the VS Code workspace.

• Welcome View:

  • Rearranged Manage SDKs menu to include and always allow Manage West Workspace actions.
  • Stopped showing a quick pick step for selecting a toolchain or an SDK when there is only one to uninstall.
  • Introduced the concept of the last used SDK and toolchain versions.

• Application View:

  • Added toolchain and SDK selection to Build Configuration pages.
  • Added toolchain validation to the Build Configuration page.

• Actions View

  • Changed all actions to use the SDK and toolchain version of the active context when working with builds.
  • Changed all actions that need an SDK version to prompt the user for selecting one. This is only valid when not working with an active context.
  • Changed the Pristine Build action to use the SDK and toolchain version of the active context.

• Source Control UI

  • Cleaned up the selection of the SDK workspace and the west manifest file.

• Settings and commands

  • Updated west workspace management, which includes commands and workflows for workspace initialization and update.
  • Refactored C/C++ IntelliSense configuration to remove fallback on the active SDK and toolchain.
  • Deprecated nrf-connect.topdir and nrf-connect.toolchain.path settings.
  • Removed obsolete actions that were referring to "active SDK" and "active toolchain".

• Notifications

  • Removed obsolete notifications that were referring to "active SDK" and "active toolchain".
  • Removed a warning about unconfigured extension.

---