We don't actually want this because it means a locale of "en-US-blah" will only match snippets made available in en-US, and thus may skip out on a custom client match rule that matches the en-US-blah locale.

I would actually have this just check if their locale is in the `LANGUAGE_VALUES` list and filter by it intesad of using first. Post-release we'll probably want to update this as I've realized there are a few flaws in how we currently do this filtering that makes it hard to do certain things with client match rules.