add child questions backend code

[MaHaWo]

• add ChildQuestion and ChildAnswer database models
• add default child questions which are added when the database is initialized
  • name
  • birth date
  • remarks
  • optional file upload for image
    These are intended to fill the Child model upon registration of a new child. They have fixed question-ids of 1 to 4 in the ChildQuestion table in the above order.
• add tests for new code
• unify model classes via inheritance for questions, answers where easily possible, i.e., where no sql tables are involved.
• sonarcloud complaint is about about duplication in autogenerated code. Not sure if this should be adressed.

a substantial chunk of the changed LoC is autogenerated openapi code, so this PR isn´t quite as big as it seems.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 29.07%. Comparing base (06f1284) to head (c90409d).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #146      +/-   ##
==========================================
+ Coverage   26.83%   29.07%   +2.24%     
==========================================
  Files          93       93              
  Lines        3455     3529      +74     
  Branches      122      122              
==========================================
+ Hits          927     1026      +99     
+ Misses       2461     2436      -25     
  Partials       67       67              

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

[lkeegan]

lgtm! some minor comments

[lkeegan]

I think adding default questions to the database is a good idea - not sure about including the date of birth though as:

• it's already part of the child model (since we need it to determine which milestones a child gets)
• also I think it was only year/month in the initial requirements (opened an issue for this full date of birth for children? #147)

[MaHaWo]

the problem is here that the data of the child gets sourced through the same interface, i.e., ChildDataInput.svelte. For the user, we don´t have this because the user needs credentials upon registration and the questions then are a whole separate thing. So, unless we want to do something similar for the child (which from a user perspective would be a bit weird imho, but tolerable), we have to put entries for name and birth month/year/whatever into the questions table, and they need to be default questions because any new child MUST have them. The full date comes in b/c I think it's a more usable component in the frontend to have the usual calender selection widget rather than having to type out month and year.

[MaHaWo]

ok, so after our discussion, I removed the default questions. I believe that we would need some input to know what would be reasonable defaults, and the 'remark' question that was left after removing the ones that populate Child objects didn't seem useful enough to put in as a fixed thing.

[sonarcloud]

Quality Gate failed

Failed conditions
7.0% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

[MaHaWo]

@lkeegan you want to have another look?

[lkeegan]

lgtm!