improve UX of (upload) select box

[martenson]

I encounter this regularly on upload, but it is likely happening in other contexts. When you specify a string to filter on, the suggested values are results of fulltext search ordered alphabeticaly even if you have an exact match. Two examples below

above I would argue that a better order would be fasta as an exact hit (thus confirmed by Enter)

---

Here I would expect tsv

[hexylena]

preferring the exact prefix matches when ranking results would be so helpful!

[mvdbeek]

Finally found @jmchilton's #16564, this should be a good compromise for nonsense values like fastq, csfasta and so on, we just need to extend the values.

[jmchilton]

That is why I thought the backend enabled fix would be easy... I did it... and not like years ago 🙈. Past @jmchilton creates a lot of problems but sometimes has some okay ideas.

[mvdbeek]

Ah, we should also show the same warning in the single item datatype selector:

[mvdbeek]

This is probably more used then the set all box, at least that's the case for me personally.