[candidate_parameters] Family tab rely on options from SQL instead of redefining them in JS

[HachemJ]

Brief summary of changes

Load relationship options dynamically from the database and remove hardcoded values from the frontend.

Testing instructions (if applicable)

1. Source the database.
2. Run the patch.
3. Verify that the family table contains a new column named RelationshipLabel and that all rows have been populated correctly based on their Relationship_type.
4. Go to the Family Information tab. (The Candidate parameters module is reachable by going to access profile (candidate_list) --> click on a candidate --> click on candidate info)
5. (Optional) In some cases the Family tab is unaccessible if the study configuration does not have it enabled (check config module). You can also enable it from going to Admin --> Configuration --> select useFamily --> Submit.
6. Once on the Family Information tab for a given candidate, try deleting or adding rows in the DB and verify that you are able to control the list by adding/removing rows from the DB directly.
7. If so, success.

Do not expect a successful submission if you try adding a full sibling/half sibling or first cousin between candidates. The functionality currently seems broken on main. #10511

Link(s) to related issue(s)

• Resolves [candidate_parameters] Family tab should rely on options from SQL instead of redefining them in JS #10499

[ridz1208]

instead of doing the pselect + a forloop. use the pselectWithIndexKey() dataabse class function

[HachemJ]

implemented change + adapted js, working as intended.