Hotspot client and data type improvements

[onursumer]

What? Why?

Cancer Hotspots API client and data type improvements

Checks

• 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.
• Follows the Airbnb React/JSX Style guide.
• Make sure your commit messages end with a Signed-off-by string (this line
  can be automatically added by git if you run the git-commit command with
  the -s option)

[onursumer]

Integrate Mutation Hotspots into the Mutation Table [Uses External API]

[onursumer]

Integrate 3D Hotspots into Mutation Table

[adamabeshouse]

LGTM. Could you explain what you've improved about the client? I see the changes but don't understand enough about it to understand their significance.

[onursumer]

@adamabeshouse Actually, I improved the cancer hotspots API, and re-generated the client code here. So, I should've said "updated the client" instead :)

For the actual API improvements see: cBioPortal/cancerhotspots#56. Improvements are mostly related to parameter configuration (body parameter vs. request parameter). Seems like I wasn't using the correct parameter types in the API.

[onursumer]

We are still missing the data fields for the types defined within the client, but we can deal with it later. Hopefully updating the code generator will fix that problem at some point since we don't have that problem with the online client generator (http://editor.swagger.io/)