Imported react-mutation-mapper repo

[onursumer]

• Imported react-mutation-mapper repo with commit history using lerna import (number of commits is intentional)
• Updated dependencies and scripts to integrate react-mutation-mapper
• Cleaned up readme and docs

Checks

• 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!

[onursumer]

The only commit that needs to be reviewed is 41e7450. The rest was imported from react-mutation-mapper repo.