data(RD3): Improve measurements table

[willemijn-oudijk]

What are the main changes you did

This PR addresses the improvements on the measurements table as suggested in Epic #1084.

• Make variable required and part of composite key. This is necessary for the cases where multiple measurements are added for one individual with the same code.
• The code ontology needs to be extended, it should include biosciences EDAM terms. For now, the parents of the duplicate ontology values (e.g., metatranscriptomics) were removed. These will need to be included after multi-parent ontologies are allowed: spike: multiparent ontologies [requires design discussion if this will be a new type] #5060

How to test

• Go to the preview and sign in as admin
• Create a new schema using the PATIENT_REGISTRY template and load demo data
• When the schema has been created, go to the measurements table.
• Enter a new individual and see that variable is required. Additionally you can check if you can enter another measurement for the same individual with the same code.
• Find a term from EDAM, that is not from 'omics' (omics was solely included in the code ontology).
• See if this term is an option for code.

Checklist

• updated docs in case of new feature
• added/updated tests
• added/updated testplan to include a test for this fix, including ref to bug using # notation
• adjust demo data (if necessary)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud