Release PR#2 Release version will load dynamically from version.json

[ihsaan-ullah]

@ mention of reviewers

@Didayolo @ObadaS

A brief description of the purpose of the changes contained in this PR.

This PR makes the version number to show dynamically from the version.json file.

Issues this PR resolves

• Release version #1582 -> Point 3

A checklist for hand testing

• check that when you have json file it loads the correct version and you can click and go to the release page

Checklist

• Code review by me
• Hand tested by me
• I'm proud of my work
• Code review by reviewer
• Hand tested by reviewer
• CircleCi tests are passing
• Ready to merge

[ObadaS]

To summarize the automation of the versions.json file:

1. After we merge develop into master, we create a Github release to describe all the changes that happened, bumping the version.
2. Once we create a new Github release, Github actions will launch a workflow to change the content of the version.json file, updating it then merging it into develop directly.
3. We will then need to do another Develop -> Master merge to update the version.json file. This will allow the website to dynamically show the latest version number (it won't show it after our first develop -> master merge)

To test this once it's released, I will wait until the changes have been merged to publish the newest release notes, so that we can test the Github actions script as well as the new workflow we will have to follow after each new version.

[Didayolo]

To summarize the automation of the versions.json file:

1. After we merge `develop` into ` master`, we create a Github release to describe all the changes that happened, bumping the version.

2. Once we create a new Github release, Github actions will launch a workflow to change the content of the `version.json` file, updating it then merging it into `develop` directly.

3. We will then need to do another `Develop -> Master` merge to update the `version.json` file. This will allow the website to dynamically show the latest version number (it won't show it after our first `develop -> master` merge)

To test this once it's released, I will wait until the changes have been merged to publish the newest release notes, so that we can test the Github actions script as well as the new workflow we will have to follow after each new version.

@ObadaS Couldn't we edit version.json on develop directly before creating the release? Then we avoid multiple merging. The problem is that the URL of the release would not exist yet at the moment of the merge develop --> master.