Update GitHub workflow action for automated VSCode marketplace publishing

[Ismoh]

There is already some workaround/preparations, but I don't like it a lot.
action
custom local VSCode task

I prefer GitHub workflow action to do everything, which is necessary, but we first need to make a decision on #11

[sewbacca]

Yeah it would probably be best if building is done by CI.
I find it weird, that the compiled .js, .map files and the lldebugger.lua file are all in the code tree, as they should always be generated from the source files anyways. The only upside I can see is referencing Lua transpiled code in issues, since that is, what people will see, wenn something goes horribly wrong. However I believe this is what has lead the perfectly reasonable PR #10 being merged into a a null version with no new content being published.

On a tangental note: I probably messed up v0.3.8: I was trying to get comfortable with publishing, but I had to do lot of force pushing back and forth. I tested the release, and my fixes seem to went through anyways. However I am not sure if your merge has been correctly published. Do you want to manually reupload v0.3.8 or do we just wait until the next version?

[Ismoh]

I prefer to add generated files to version control, unless it isn't usually. It's just because of my experience I did the last 10 years in coding, because there is a proper history of changes. There are enough pros and cons for removing those files from version control system. I am open for suggestions.

Regarding publishing a new version, it is prepared. There are still some manually tasks to do, but I take a look now to automate those as well.

Offtopic: Is there a way to contact you out of github scope. Writing comments isn't the fast and best way to communicate, in my opinion. As you like.

[Ismoh]

If this debugger is frequently improved or changed, we should consider using semantic-release, but for now I simply add a more stupid and quick solution for increasing versions.

[Ismoh]

Need to adjust master, because I am not able to run the new GitHub action as long as it wasn't merged into master:
https://stackoverflow.com/questions/63480433/how-can-i-run-a-github-action-from-a-branch-other-than-master#comment135430094_67847408

[Ismoh]

For future releases the publish workflow is:

1. Do your code changes
2. Change CHANGELOG.md to your proper comming version, i.e.: b7e08d5
3. Create a PR
4. If merged run https://github.com/Ismoh/local-lua-debugger-vscode/actions/workflows/release-tag.yml
5. VSCode publish is triggered automatically afterwards