feat: Adopt Semantic Versioning (SemVer) for versioning consistency

[ColorfulRhino]

Hello!

I’ve been using the app for a while now and noticed that the current versioning scheme follows a pattern like v0.5.5k, v0.5.5l, v0.5.5m, v0.5.5n etc. While this works, I wanted to suggest considering a shift to Semantic Versioning (SemVer) to improve version tracking and user understanding. SemVer is widely used by many projects including many Android apps.

Semantic Versioning uses a format of MAJOR.MINOR.PATCH, where:

• MAJOR version changes introduce backward-incompatible changes (breaking changes).
• MINOR version changes add functionality in a backward-compatible manner.
• PATCH version changes fix bugs or make small improvements in a backward-compatible manner.

For example:

• If a breaking change was introduced, you’d update the major version (e.g., v2.0.0).
• If a new feature was added, you’d increment the minor version (e.g., v1.1.0).
• If only a bug fix was made, the patch version would be incremented (e.g., v1.0.1).

Looking at RethinkDNS's releases, every release after v0.5.5f has the note is a fast-follow release, which means v0.5.5f could have been for example v0.6.0 and the following bugfix releases could have been v0.6.1, v0.6.2 and so on.

Adopting a SemVer system could improve clarity for users, developers, and anyone relying on the project, especially when tracking updates or integrating with other services.

I believe this change could help provide better version management for the app and make it easier to understand the impact of each release.

Thanks for considering this suggestion!