Use tagged releases once we're "stable" and prevent breaking main branch

[JPustkuchen]

As the project becomes more and more stable, for further development (once it can be seen as "stable" - not before), we should ensure not to break the master branch with ongoing development.

As it might be critical to be able to use this tool reliably, development should happen in feature branches and the tool should have tagged releases.

The example clone command should in the README should always use the stable version.

[joshsedl]

I think this is a good idea, we should discuss if we want to create a release soon, or wait for correctly attached settings / extensions on startup, see #74.

I think a "soonish" release would be fine, since the current workaround, using workspace settings + extension installation through @recommended is enough and when the feature in #74 is implemented it will probably have more flaws, than our current setup.

[JPustkuchen]

Yes, we can do a release, but I'd vote for 0.1.x (pre-stable) and with #74 it would for example become 0.2.x... until one day we will (or not) decide for 1.x