Register title and subtitle

[MartinBenediktBusch]

Overview

This PR adds a questionOptionType column to the registrationFields data table, which allows to identify whether a registration field is a TITLE or SUBTITLE. Furthermore, the PR changes the reference field in the questionOptions table from the registrationFieldId to the registrationId as the registration id is the same for different registration fields belonging to the same user. Lastly, the PR updates and refactors the updateQuestionOptions function to allow for the automatic updating of title and subtitle information for the same question options.

Note that the implemented functionality is targeted solely to the berlin usecase. This is a little bit of a drawback as multiple events and multiple question_ids might not work with the implemented changes. This required a more general setup beyond the berlin usecase.

Details about the registration data service update

This PR refactors the updateQuestionOptions function to implement the required functionality and improve code clarity. The main changes include:

• Created separate functions for fetching registration fields, filtering registration data, mapping to combined data, and updating/inserting question options. The original monolithic updateQuestionOptions function is refactored into smaller, more focused functions, each responsible for a specific task. This improves readability and maintainability by breaking down the complex logic into reusable components.
• New Functions: Two new functions, filterRegistrationData and mapToCombinedData, have been introduced to handle intermediate processing steps:
  • filterRegistrationData: Filters registration data based on the available registration fields. It takes an array of registration data and registration fields as input and returns filtered registration data that requires updating.
  • mapToCombinedData: Maps filtered registration data to a combined format suitable for updating/inserting question options. It takes filtered registration data and registration fields as input and returns combined registration data with values grouped by question option type.

Testing

• Remember to test this locally as datatable changes have been made.

[diegoalzate]

i like the decoupling, some small changes requested