feat(openchallenges): implement input data type filter on challenge search page

[rrchai]

• closes [Feature] Create a filter component for challenge input data types #2578

The filter should now be able to search the EDAM data concepts and be used to filter challenges.

Changelogs

• enable to list out EDAM data results (sorted alphabetically) in the input data type filter
• enable to search data type by keywords in the search bar of the filter
• enable to filter challenges by input data type keywords in the search bar of the page
• enable to filter challenges by selected input data type(s)

Preview

---

There is a bug I notice for the search dropdown filter - tracked #2648, and will be fixed in a future pr.

[sonarqubecloud]

Quality Gate passed for 'openchallenges-app'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[tschaffter]

The new component works as described.

How does the bug that you mention and are fixing in another PR affects the shipping of the present PR?

• Do you plan to merge the second PR into this present PR, then merge it to main?
• Do you want to merge this PR into main first, then merge the second PR to main?
  • This is OK if you consider that the first PR could potentially be shipped to prod without the fix. We could also wait for the fix to be ready before merging the two PRs consecutively.

One concept that may help here and for sure in the future are "feature flags". Here, we could show/hide the new UI component using a boolean flag in the app config. Lets discuss this strategy next time we meet!

[rrchai]

How does the bug that you mention and are fixing in another PR affects the shipping of the present PR?

• Do you plan to merge the second PR into this present PR, then merge it to main?
• Do you want to merge this PR into main first, then merge the second PR to main?

Since this bug has already been there on the prod site for other filters like organization, I prefer to merge this PR first once approved, and then I will fix the bug in a separated PR.