Use "patch" for extension versioning

[divyenduz]

With this PR #109, we implemented required changes for #93

But because of the marketplace limitations, it is not yet possible to have strings in a version: microsoft/vscode-vsce#148

Because of this release CI is broken right now and we are figuring out a way to translate Prisma version to VSCode extension version. Also supporting independent extension releases with the process

While we work that out, we can use the "patch" strategy for extension versioning in the CI. This is the approach we were using before #109 was merged

Essentially, for every release, simply patch the version by one number independent of the Prisma version

Examples:

• Prisma extension goes from 0.0.32 (current) -> 0.0.33 -> 0.0.34 and so on irrespective of why a release happened

• Prisma Dev extension goes from 0.0.1 (current) -> 0.0.2 -> 0.0.3 and so on irrespective of why a release happened

• If we want to intervene the versions for any reason, we can manually push say 0.0.x and the next patch will automatically be 0.0.x+1

[divyenduz]

Note: Since, I can't get the published extension version from marketplace. I need to write that into a file again, one for each channel (say prisma_version_stable, prisma_version_unstable).

We only commit from the unstable channel but we have to commit this version file also from the stable channel.