- Update all paths
- Change router to use children instead of render props
- Remove legacy app chrome

- Update all paths
- Use global flash messages

- Update all paths
- Use global flash messages
- Add types to fix errors
- Use React Router Hooks instead of legacy withRouter HOC

This is not needed because the ID is actually passed in the URL itself and is not a requirement in the body of the request

It appeared that the server sometimes sent flash messages with the API response, but I checked the Rails server code and there is no `flashMessages` sent back from the server so I am omitting that from the `RoleMappingsServerDetails` interface as well.

I did this for RoleMappings but forgot this one

Because the shared role mapping components work for both App Search and Workplace Search, the more generic string is used here because App Search has different role names.

In the case of a new role mapping, the server is called at the ‘/new’ route and the server responds without a roleMapping prop, as it has not yet been created.