ci: Remove backport automation (#242)

We're not currently using this, so removing it for now. We might move to
releasing from main, which would remove the need to backport.

closes #220
closes #206

Signed-off-by: Tyler Smalley <[email protected]>

Author: Tyler Smalley

.backportrc.json

@@ -67,10 +67,6 @@ To debug webviews in our VS Code extension, you can access the Developer Tools b
 
 We make use of [Webview UI Toolkit for Visual Studio Code](https://www.npmjs.com/package/@vscode/webview-ui-toolkit), specifically for its [React Components](https://github.com/microsoft/vscode-webview-ui-toolkit/tree/main/src/react)](https://github.com/microsoft/vscode-webview-ui-toolkit/tree/main/src/react) which are wrappers around the components. These components follow the design language of VS Code to maintain a consistent look and feel.
 
-### Backporting
-
-To backport a PR, add the `auto-backport` label to a PR and a corresponding version label (example: `v0.4`). Once the PR is merged, a corresponding backport PR will be created against the release branch.
-
 ## Release Process
 
 #### To make a new minor release. (e.g., `0.2` ⇒ `0.4`)

.github/workflows/backport.yml

@@ -465,7 +465,6 @@
     "@vscode/codicons": "^0.0.33",
     "@vscode/vsce": "^2.21.0",
     "@vscode/webview-ui-toolkit": "^1.2.2",
-    "backport": "^8.9.8",
     "bufferutil": "^4.0.7",
     "concurrently": "^8.2.2",
     "css-loader": "^6.8.1",