Profile ID for study flow methods

Study flow methods accept a manually selected profile id, which however is checked against the user token infos. The token must include the profile ID (as main or other), otherwise a log event is saved and the method return permission denied error.

Improved Logging and Assigned Surveys workflow

Important

The service needs a new environment variable ADDR_LOGGING_SERVICE, to be able to connect to the logging service.

Changes

• Connect to logging service over grpc to be able to log important events regarding study management and accessing data by researchers and admins.
• GetAssingedSurveys endpoint returns all assigned surveys for the user - every profile from every study they are in together with survey infos (once per study), so that the client can have all the necessary infos after one single http-call.

v0.11.1

• fix bug about participant flags not included when no context rules

v0.11.0

This release implements:

• expression to check submitted response if it contains any of the specified keys (works similar than the client method)
• lookup participant state and include flags into the survey context when sending assigned surveys

v0.10.1

• don't accept empty response array - however more complex validations needs to be done on the client-side for now

v0.10.0

• update study model to include study stats
• update survey model - move name and description to props and add new attribute about typical duration

v0.9.0

• use centrally defined api definitions
• re-use token checking code
• add survey category with logic
• other code improvements

v0.8.0

Add endpoint and logic for removing participant data from studies

v0.7.3

Improvement: Add localisation possibility to study tags

v0.7.2

• cache previous surveys if needed to retrieve items from them more than once