Trigger first release to open-vsx.org

This is the first try, so we may need to adjust some things to
make it work in the end.

The idea is to update file RELEASE, adding a new release tag in there.
Then we expect that tentative, automatically-generated release notes,
will be added to this PR, for our review. Once we merge the PR, a
GitHub release v0.2.0 should be created automatically in the repo,
with attached release notes. The tag's creation should then trigger the
job that published the extension to open-vsx.org.

Note: I picked v0.2.0 to avoid conflicting with the "vscode trace
extension", that's already released on the Visual Studio Marketplace
(which is currently at v0.1.44). I propose we go with a v1.0.0 version
after discussions with other contributors, and after our release/publish
infrastructure has been demonstrated to work well.

Signed-off-by: Marc Dumais <marc.dumais@ericsson.com>

Author: marcdumais-work

RELEASE

@@ -1 +1,7 @@
 # Release file - see documentation: https://github.com/pipe-cd/actions-gh-release#usage
+
+tag: v0.2.0
+
+commitExclude:
+  prefixes:
+    - "Merge pull request #"

vscode-trace-extension/package.json

@@ -2,7 +2,7 @@
   "name": "vscode-trace-extension",
   "displayName": "Trace Viewer for VSCode",
   "description": "Viewer that permits visualizing traces and contained data, analyzed by a trace server, and provided over the Trace Server Protocol (TSP)",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "license": "EPL-2.0",
   "engines": {
     "vscode": "^1.52.0"