Merge branch '29-as-a-client-i-want-to-consume-the-result-of-the-descriptive-statistics-algorithm-so-i-can-render' into 31-as-a-client-i-want-to-be-able-to-query-specific-fields-in-experiment-result-api-so-that-i-only
Update branch 31 with last features on Experiment from branch 29

GraphQL transient calls working with real Exareme calls

WIP : Converter for exareme

Resolve "Add root group info to pathologies to build treeview in frontend"

Closes #30

See merge request sibmip/gateway!9

Merge branch '7-as-a-client-i-want-to-be-able-to-query-specific-fields-in-pathologies-api-so-that-i-only-get-what' into 'develop'

Resolve "As a client, I want to be able to query specific fields in pathologies API so that I only get what I need"

Closes #7

See merge request sibmip/gateway!7

Added flatten groups

Merge branch '5-as-a-client-i-want-to-be-able-to-query-my-settings-through-the-gateway-so-that-it-s-no-more' into 'develop'

Resolve "As a client, I want to be able to query my settings through the gateway so that it's no more related to the engine"

Closes #5

See merge request sibmip/gateway!6

Merge branch '24-as-a-developer-i-want-to-use-husky-so-that-i-can-keep-my-code-clean' into 'develop'

Resolve "As a developer, I want to use husky so that I can keep my code clean"

Closes #24

See merge request sibmip/gateway!5

Merge branch '15-as-a-developer-i-want-to-design-the-metadata-schema-in-order-to-implement-the-api' into 'develop'

Resolve "As a developer I want to design the metadata schema in order to implement the API"

Closes #15

See merge request sibmip/gateway!4

Merge branch '4-as-a-client-i-want-to-query-the-experiments-so-that-we-manage-a-unified-api-url' into 'develop'

Resolve "As a client, I want to query the experiments so that we manage a unified api url"

Closes #4

See merge request sibmip/gateway!3

Resolve "As a client, I want to query the algorithms so that it does not call the engine directly"

Closes #6

See merge request sibmip/gateway!2