Feature/remove commit register mapping

[gibkigonzo]

Short description and why it's useful

I know that good practice is to use commit instead of mutation, but this commit kills vue-devtools. 90% of commits in timetravel in vue-devtools are REGISTER_MAPPING. I think that we don't even want to check previous state of route mapping because it's more like data aggregate. Vue-devtools makes copy of vuex state with every commit to allow timetravel and sometimes it can't handle this (check screen).

Screenshots of visual changes before/after (if there are any)

Which environment this relates to

Check your case. In case of any doubts please read about Release Cycle

• Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
• RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
• Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

• No upgrade steps required (100% backward compatibility and no breaking changes)
• I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change

Contribution and currently important rules acceptance

• I read and followed contribution rules

[pkarw]

I’m ok with this change. Please maybe just leave a comment pointing this PR to not let us forget why we did intentionally skip this good practice in here ;)

[pkarw]

@andrzejewsky as for me this is ok to merge - looking for your second approval :)

[andrzejewsky]

looks good for me, sometimes it breaks even the dev-tools

@gibkigonzo good work! even though.... again - CHANGELOG!! 😄