Fixed validation issue with different geneset_def_version

[dianab0]

The current validation process of cBioPortal does not throw an error when the property geneset_def_version is different in the study from the one in the database. This leads to an error throwing when cBioPortal tries to load the study.
Fixed it by first adding the geneset version from database to the API and also to PortalInfo, then retrieving it in the validateData.py script and comparing it to geneset_def_version in the study.

Fix # (see https://help.github.com/en/articles/closing-issues-using-keywords)

Describe changes proposed in this pull request:

• Updated the API to include the geneset version at /api/genesets/version
• Updated the DumpPortalInfo script to get the geneset from API
• Updated the validateData.py to get the geneset version from either portal info or API, compare it to the geneset_def_version in the study and return error if different.

Checks

• Runs on heroku
• Has tests or has a separate issue that describes the types of test that should be created. If no test is included it should explicitly be mentioned in the PR why there is no test.
• The commit log is comprehensible. It follows 7 rules of great commit messages. For most PRs a single commit should suffice, in some cases multiple topical commits can be useful. During review it is ok to see tiny commits (e.g. Fix reviewer comments), but right before the code gets merged to master or rc branch, any such commits should be squashed since they are useless to the other developers. Definitely avoid merge commits, use rebase instead.
• Is this PR adding logic based on one or more clinical attributes? If yes, please make sure validation for this attribute is also present in the data validation / data loading layers (in backend repo) and documented in File-Formats Clinical data section!

Any screenshots or GIFs?

If this is a new visual feature please add a before/after screenshot or gif
here with e.g. GifGrabber.

Notify reviewers

Read our Pull request merging
policy. It can help to figure out who worked on the
file before you. Please use git blame <filename> to determine that
and notify them either through slack or by assigning them as a reviewer on the PR

[oplantalech]

Thank you, @dianab0! Good work!

[dianab0]

Pushed a second commit to include the necessary changes to the test_data folder so the test scripts will work.