Set up proper release process

[kimadactyl]

Is your feature request related to a problem? Please describe.

People developing EW stories for their website need consistent story formats to build against. As the EW development team, we need to be able to continue to add features and fix bugs without breaking people's existing stories. As such, we need a proper release process for both EW users and developers.

Describe the solution you'd like

We should ust GitHub releases to carefully control the story format URLs we use in the documentation and client training.

Describe alternatives you've considered

The current solution of having the version hard coded as a directory name means we would need to keep all versions up in perpituity. This is very brittle.

Suggested steps

• Move the built format from /dist/enquirywitch-0.0.1 to simply /dist
• Use GitHub "Create a new release" feature with v0.0.1 tag to version the current release
• Use the URL created in the last named stable release for the EW distribution in training and documentation. This ensures that people will be working against a consistent EW build.
• Add release-drafter to this repo (see imok for example) and begin using semantic versioning going forwards

[jazzchatfield]

Sounds ok, but I don't know how to do any of it and I don't understand any of it haha.

What would the final URL output of both be? That might help me imagine.