Add relevance2 relevancy to the sort menu when the link_relevancy feature flag is enabled, so that the original relevance and the new relevance2 are both available as options. The relevance2 option will not be exposed in the api docs or available outside of the feature flag.
Use relevance2 relevancy when the link_relevancy feature flag is enabled. The new relevancy requires bypassing the l2cs query parser when possible so that field weights will be properly applied. This also results in a simplified search query.
There's an unidentified bug that is causing Subreddit.subscribe_defaults to run for users that have already subscribed, which results in a lot of CreationErrors that might be hurting postgres.
There may be a race condition where a user subscribes to multiple subreddits in succession. Update user.has_subscribed before subscribing to reduce the window where a user could get subscribed to the default subreddits multiple times.
We now write the data every hour (previously was once per day).
These are being used by the data team and will need to be written until they are able to read the new `SubscribedSubredditsByAccount` from Cassandra.
During the backfill for migrating from SRMember I didn't write the last modified values, so fast_query() can incorrectly bail out early and return no results if the user hasn't added any subscriptions.
The full list of a user's subscribed subreddits can be used several times in a request. Store it in the `thing_cache` local cache to avoid redundant requests to Cassandra.
Previously the note about how traffic processing works would be red whether it was currently slow or not. This makes it so that it's just black and bold if it's the normal message about processing being on an hourly basis, and red if it's the warning about things currently being slow.