MagicSearch does not filter by localized options

[Eddie Ramirez]

How to reproduce:

1. Set a different language than English (Tested with Spanish)
2. Go to Project->Compute->Images
3. Open filters and select a facet with options, e.g. "Status".
4. A menu opens with a set options (note: translated options). Type "activo" (spanish word for active).
5. See that no matches are found since "activo" is not a valid filter option in the API.
6. Try using "active" and now it works

Showing the localized options might confuse the user as they may think is a valid option but it's not. However, I believe we should keep the options localized.

[Rob Cresswell (robcresswell-deactivatedaccount)]

What seems to be happening is that if you skip the dropdown options, and type out the word, it checks that text literally against the api filter. So even under a Spanish locale, typing out "active" will produce the correct result, but "activo" won't.

The only way to practically improve this is block arbitrary user input in magic search when a dropdown is available, so they don't manually type it.

[Lucas H. Xu (xuh-2)]

I cannot reproduce this when I set the language as Chinese(Mandarin).