Fetch imaging modality options from an API endpoint instead of a using hardcoded list

[rmanaem]

Having run into the #642 we realized it might no longer be viable to store imaging modality options as a hard coded list on the query tool side and instead they should be retrieved from an API endpoint just like diagnosis and assessment tool options.

Since we will soon have more modalities, we could switch to color-coding them by the BIDS datatype (anat, func, etc.) instead of assigning a distinct color per suffix. These datatypes should be able to be read from a config file - see neurobagel/communities#43.

Tasks:

• Fetch imaging modality options from the API (nb:Image) the same way diagnoses/assessments are retrieved, replacing the hardcoded constants.
• Store modality metadata (Label, TermURL, abbreviation, data_type) and use the metadata to map result data to UI labels.
• Generate a distinct color for modality based on DataType
  • Filter out modalities that miss DataType or Abbreviation
• Update convertURIToLabel conversion logic to use fetched modality metadata instead of the static map.
• Update affected component and e2e tests
• Add tests for the new API request endpoint

References:

• BIDS datatypes (15 total): https://github.com/bids-standard/bids-specification/blob/master/src/schema/objects/datatypes.yaml

[surchs]

In neurobagel/communities#43 we have introduced the data_type attribute for imaging modalities. This attribute can define the colour of imaging tags - and later when we enable more imaging tags maybe also a grouping of tags by data type

[surchs]

Here is a list of plot related links: https://docs.google.com/document/d/1iXcf4Uf6MD37dbUtl24kb8JjBJoRKXVCyHHgz74Fp1o/edit?usp=sharing the section on color picking might be helpful