Add childquestions backend integration and refactor datainput datastructure

[MaHaWo]

What it does

• integrates backend into ChildrenDataInput and ChildrenGallery frontend component
• add delete_child_image endpoint to user backend.
• makes more use of svelte-5 runes in components related to child and data input.
• various smaller fixes mostly related to types
• modifies the FileInput component to work better with the backend system
• functionally unifies the question editing dialog for user and child questions -> EditQuestions.svelte , Question.svelte
• integrate question edition into admin page.
• add creation of new child with necessary data to the children datainput dialog. Submit and markup section handle the data that is related to the child and the data that belongs to questions separately as discussed.
• make the answer response for children a dict[id, answer] instead of list[answer]. This is a little easier to maintain in the frontend. Arguably should be the same for user answers, but not done here to not conflate things too much.
• delete frontend code that emulated backend
• delete childstore and replace with one that just stores the current child's id or null if there is none. Still using stores instead of runes here, imho they are easier to use with less code for what I need them for. Might be necessary to migrate at some point though.
• adjust python tests where necessary.
• the diff view won´t be much help for ChildrenGallery.svelte and ChildrenRegistration.svelte as especially for the latter, most of the code changed.

Questions

• do we need the 'order' parameter in the questions or can this role be fulfilled by the id?
• child image handling is a little suboptimal imho:
  • Image deletion is a bit complicated: Other question elements can be deleted by providing an empty value as input. For image files, this is not as straight forward since it's stored separately. I don´t want to do anything implicit à la "if empty string then and child had a file previously, then delete". So I added an explicit delete button if there is an image already. This is displayed in addition to the upload dialog. To make all this work and activate and deactivate at the right time, 2 new boolean flags are needed.
  • this might all simplify a bit if it turns out during milestone integration that we should store the whole child object as $currentChild and not just it's id. I was hesitant to do this right now though, because it stores a lot of data in the frontend.

closes #113
closes #112

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 3.24826% with 417 lines in your changes missing coverage. Please review.

Project coverage is 27.89%. Comparing base (52e4c51) to head (926b612).

Files with missing lines	Patch %	Lines
...end/src/lib/components/ChildrenRegistration.svelte	0.00%	205 Missing and 1 partial ⚠️
frontend/src/lib/components/ChildrenGallery.svelte	0.00%	81 Missing and 1 partial ⚠️
frontend/src/lib/components/Admin/Questions.svelte	0.00%	57 Missing and 1 partial ⚠️
.../src/lib/components/Admin/EditQuestionModal.svelte	0.00%	33 Missing ⚠️
.../src/lib/components/DataDisplay/CardDisplay.svelte	0.00%	14 Missing and 1 partial ⚠️
frontend/src/lib/admin.svelte.ts	0.00%	7 Missing ⚠️
frontend/src/lib/components/AdminPage.svelte	0.00%	7 Missing ⚠️
...tend/src/lib/components/DataInput/DataInput.svelte	0.00%	3 Missing ⚠️
...end/src/lib/components/DataInput/Fileupload.svelte	0.00%	2 Missing ⚠️
frontend/src/lib/stores/childrenStore.ts	0.00%	1 Missing and 1 partial ⚠️
... and 2 more

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #138       +/-   ##
===========================================
- Coverage   93.64%   27.89%   -65.76%     
===========================================
  Files          20       91       +71     
  Lines         850     3280     +2430     
  Branches        0       88       +88     
===========================================
+ Hits          796      915      +119     
- Misses         54     2299     +2245     
- Partials        0       66       +66     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[MaHaWo]

found a bug that slipped through the net. need to fix that before review. sry

[MaHaWo]

ok, I think I'm done @lkeegan. feel free to start whenever you have time.

[lkeegan]

lgtm - some minor comments/suggestions.

re questions:

1. we need order if we want the admins to be able to change the order of the questions, if they are fine with them coming in the order that they were added to the database then yes we can remove it (same goes for milestonegroup)
2. image handling: do we need to be able to delete the image - or is just allowing the user to upload a different one sufficient?
3. yes I would store the child object

[MaHaWo]

thanks for the input. Regarding image deletion:

• I think we should be able to delete it:
  • users might just change their mind.
  • user might upload an image but later find out they were not allowed to/ did so on accident or are not allowed anymore.
  • it might be more convenient to have no images when the number of observed children grows - kindergarden or the like.
    => therefore, option to delete image would be nice to have.

[sonarcloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[MaHaWo]

I added the default image for image-less children now, too.