The legacy language warning was misfiring when a user's language
didn't match the APP_LOCALE from .env.
Additionally, we weren't properly warning when the legacy-language
came from Settings or from the user themselves. Both of which should
be impossible but still probably not a bad idea to warn on it, anyways