Split AppRouter routes to multiple sub-routers based on top-level routes

[rithviknishad]

Advantages:

• Cleaner codebase
• Reudce API calls to fetch parent route datas
• Improve codeclimate score

For example:

For every facility page we visit (/facility/{id}, /facility/{id}/configure, /facility/{id}/beds) we keep fetching the facility record for the breadcrubms and other things to work on every page visit.

However, with this approach, we can have a FacilityRouter which will wrap all facility routes under a ContextProvider that'll pass the current facility's data, and hence the facility read API is dispatched only once every time we enter a facility specific route.

<FacilityProvider>
  <FacilityConfigurePage> // or any other facility route page
</FacilityProvider>

[rithviknishad]

To skip the caching and provider concept and just to split the app router