Dev workflow: Bump version with the first PR that introduces change

[psrok1]

Your checklist for this pull request

• I've read the contributing guideline.

What is the current behaviour?

Although current master branch contains new features under development, it has the same version number as latest release. That may be misleading for mwdb-core users.

It's a good practice to bump version with the first pull-request, so version number in master branch always fulfills the semantic versioning requirements.

What is the new behaviour?

• Because version bump requires to change all the 6 files that contain the version number: added helper script dev/bump_version.py that assists in that change.
• Added bump recommendation to CONTRIBUTING.md
• Bumped version to 2.3.0 to apply the recommendation to current master branch, which introduces new features comparing to the current stable.

Example output from dev/bump_version.py:

$ python dev/bump_version.py 2.3.0
=== /home/psrok1/mwdb-core/setup.py
--- 
+++ 
@@ -7,7 +7,7 @@
 """
 
 setup(name="mwdb-core",
-      version="2.2.2",
+      version="2.3.0",
       description="MWDB Core malware database",
       long_description=LONG_DESCRIPTION,
       author="CERT Polska",
=== /home/psrok1/mwdb-core/mwdb/version.py
--- 
+++ 
@@ -4,5 +4,5 @@
 except IOError:
     git_revision = ""
 
-app_version = "2.2.2"
+app_version = "2.3.0"
 app_build_version = f"{app_version}+{git_revision}" if git_revision else app_version
=== /home/psrok1/mwdb-core/mwdb/web/package.json
--- 
+++ 
@@ -1,6 +1,6 @@
 {
   "name": "mwdb-web",
-  "version": "2.2.2",
+  "version": "2.3.0",
   "private": true,
   "dependencies": {
     "@fortawesome/fontawesome-svg-core": "^1.2.0-14",
=== /home/psrok1/mwdb-core/mwdb/web/package-lock.json
--- 
+++ 
@@ -1,6 +1,6 @@
 {
   "name": "mwdb-web",
-  "version": "2.2.2",
+  "version": "2.3.0",
   "lockfileVersion": 1,
   "requires": true,
   "dependencies": {
=== /home/psrok1/mwdb-core/mwdb/web/src/commons/package.json
--- 
+++ 
@@ -2,7 +2,7 @@
     "name": "@mwdb-web/commons",
     "main": "index.js",
     "private": true,
-    "version": "2.2.2",
+    "version": "2.3.0",
     "peerDependencies": {
         "@fortawesome/react-fontawesome": "*",
         "lodash": "*",
=== /home/psrok1/mwdb-core/docs/conf.py
--- 
+++ 
@@ -21,7 +21,7 @@
 author = 'CERT Polska'
 
 # The full version, including alpha/beta/rc tags
-release = '2.2.2'
+release = '2.3.0'
 
 
 # -- General configuration ---------------------------------------------------
[*] Check above diff ^ Is it correct? (y/n): y
[+] Changes applied!

[chivay]

:wew:

[ITAYC0HEN]

I think that a safer idea might be to add this to the release procedure. that means, that after a release, you will commit\pr the version bump.
So instead of waiting for some random change, it will be in the TO-DO list of the release procedure.