Define which data should be send to the mobile app (informant & officers) [2] about sormas-project

@MartinWahnschaffeSymeda Solution B is to make all data of the officer's regional area (LGA) available on the phone. In this scenario the list of cases, contacts and events should by default filter to the entries of the officer.

@MartinWahnschaffeSymeda Please note that this is for the contact officers/surveillance officers and ofcourse the supervisors. The excerption rule is the hospital informant. Only solution A applies to Hospital information @gstephan30

[StefanSzczesny]

Implementation:

• informant: all data associated to the facility (cases)
• officers (all): all data associated to the LGA (cases, events)
• all data that is created by the user
• all data associated to the above data (contacts, tasks, persons, visits)
• special case: if an officer has access to task or contact whose case/event/contact is not available, the association link should be inactive
• "sync all" button in app menu (if possible)
• "drop data" button in users screen
• time period is not needed for prototype

[StefanSzczesny]

There are sync issues while loading event from task side. Moved this from #67.

• check event ID in task list
• check link to event from task

[StefanSzczesny]

Moved the refresh after saving (push to server-side) matter from issue #68.

• think about an unified refresh concept for each saving

[MartinWahnschaffe]

In addition to the stuff above I have done the following:

• add health facility to informant (backend, dto, ui, app)
• include user in person rest sync
• persons of cases and contacts
• visits of the contacts persons
• tasks of cases, events, contacts

the tasks "sync everything" und "unified refresh concept" should probably put into a new issue in the backlog.

[MartinWahnschaffe]

• create docu file that explains what is synced

[MartinWahnschaffe]

See https://github.com/hzi-braunschweig/SORMAS-Open/blob/development/sormas-backend/doc/UserDataAccess.md for the documentation.