Handle switching editors with unsaved edits

[zlavergne]

There was a problem reported with the RapiD integration when a user would attempt to switch editors from RapiD to iD when the user still had unsaved edits (#5025)

This PR does 3 main things to solve this issue:

1. Uses the UnsavedMapChangesModalContent component to show an alert if a user still has unsaved edits and tries to switch editors
   
2. To make the actual component switch more performant, I changed how the editor switch is handled. Before, if you switched between RapiD and iD, it would reload the entire page; now it will only reload the single editor components.
3. To allow (2) to happen, I had to add a RAPIDCONTEXT to the redux store so the contexts don't get confused during the switch since they have slightly different values in their contexts.

Closes #5025

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

No Coverage information
0.9% Duplication

[HelNershingThapa]

I've added an error popup that shows up when trying to switch to JOSM. Other than that, I tested the switching process locally, looks good to me @Aadesh-Baral

[HelNershingThapa]

Will removing the previously installed RapiD dependency(rapid-v1.1.8_tm) be safe?

[zlavergne]

It should be totally safe. Making the editors be different components instead of reloading the page required a few changes to RapiD as well. It will basically function as an update to the RapiD dependency.

[HelNershingThapa]

Removed on 27ab132