Optimising reset sync

[mahalakshme]

Current scenario:

-- Necessary improvements to make the sync specific to subject type is already made
-- With change of address level we are doing full reset, since its complex to handle and not a frequent scenario
-- Reference data need not be deleted when doing reset sync

Improvements that can be made:

• when a user has reset sync and fast sync both, the fast sync is downloaded and then the user is presented with option to reset sync, which can be confusing - https://app.zenhub.com/workspaces/avni-product-deprecated-635b73bded85e50018871ae6/issues/gh/avniproject/avni-server/471 - very less probability
• Do not delete the non scoped entities when doing full reset sync
  --- there are around 51 non-scope entity and with concept also being non-scoped(with some orgs with 5000 concepts), - this can save around 3 min for the user
• When few addresses are removed/added to a catchment, do a selective sync instead of full reset sync
• Better user messages:
  ----- In getSyncDetails show FetchingChangedResource
  ----- When doing getResetSyncData show 'Checking if your settings are updated'
  ----- When doing ResetSync() show 'Resetting data since your settings are updated'
  ----- For all the above 3, add the necessary platform translations