update repo metadata (#792)

Author: joaomoreno

.vscode/settings.json

@@ -15,6 +15,5 @@
 	"[typescript]": {
 		"editor.defaultFormatter": "esbenp.prettier-vscode"
 	},
-	"conventionalCommits.scopes": ["api"],
 	"git.branchProtection": ["main"]
 }

README.md

@@ -2,9 +2,8 @@
 
 > _The Visual Studio Code Extension Manager_
 
-[![ci](https://github.com/microsoft/vsce/workflows/ci/badge.svg)](https://github.com/microsoft/vsce/actions?query=workflow%3Aci)
-[![Version](https://img.shields.io/npm/v/vsce.svg)](https://npmjs.org/package/vsce)
-[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
+[![Build Status](https://dev.azure.com/monacotools/Monaco/_apis/build/status/npm/microsoft.vscode-vsce?repoName=microsoft%2Fvscode-vsce&branchName=main)](https://dev.azure.com/monacotools/Monaco/_build/latest?definitionId=446&repoName=microsoft%2Fvscode-vsce&branchName=main)
+[![Version](https://img.shields.io/npm/v/@vscode/vsce.svg)](https://npmjs.org/package/@vscode/vsce)
 
 ## Requirements
 
@@ -96,8 +95,6 @@ Once the watcher is up and running, you can run out of sources with:
 node vsce
 ```
 
-This project uses [semantic-release](https://semantic-release.gitbook.io/semantic-release/) and commit messages must follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) spec. This allows us to effortlessly automate releases.
-
 ## About
 
 This tool assists in packaging and publishing Visual Studio Code extensions.