Description

In #12094 we changed frontend redirects from 302 to 301. Unfortunately this means if we enable a new locale, and a user has previously attempted to use that locale in a url, then that user won't get to experience the new locale - their browser will have permanently cached it was unavailable.

To allow a better experience for future new locales, we should stop using 301 for locale redirects. (We probably do want the reasons for a redirect to still be permanent tough, just not locale related redirects)

Acceptance Criteria

• a redirect from /foo-baa/firefox/ to /en-US/firefox is sent as a 302

┆Issue is synchronized with this Jira Task