Add releases / version numbers

[NicoWeio]

Since BeFake is a good candidate for automated running, adding releases / version numbers could allow users to

• distinguish between breaking/non-breaking changes (assuming semver)
• update to the latest minor version automatically
• get notified on new releases (using GitHub's watch options)

Note that version 1.0.1 is currently specified in some places, such as https://github.com/notmarek/BeFake/blob/06f9cc709ecbd71b2c14e4b8c3b9d612fc5e5904/pyproject.toml#L6 and https://github.com/notmarek/BeFake/blob/06f9cc709ecbd71b2c14e4b8c3b9d612fc5e5904/setup.py#L5

[Smart123s]

I support this idea (I'm running BeFake as a cron job, so stability would be good there). The only reason the default save locations are crap (https://github.com/notmarek/BeFake/issues/62) is because I didn't want to introduce breaking changes. However, some serous changes should be made to the code before staring proper releases (that follows the semver specifications?).

For example, adding extra bereals (https://github.com/notmarek/BeFake/issues/87) on top of the current default filenames (and --save-location flags) would be awful.

My recommendation would be to create a release once https://github.com/notmarek/BeFake/issues/89 is fixed (I though my PR fixed it, but it didn't, it should be reopened), and then make a ton of breaking changes, and then start creating proper releases. The code is nearing a point both in complexity and in quality, where proper release are starting to make sense.