LPS-48695 Store availableLanguageIds in the index for journal (like we do in the XML)
LPS-48695 Get snippets from the localized assetCategoryTitles fields (Lucene)
LPS-48695 Get snippets from the localized assetCategoryTitles fields (Elasticsearch)
LPS-48695 Consider matches in the localized assetCategoryTitles fields when we create summary for journal. When,

- there is a WC with 2 locales: en_US, fr_FR
- en_US is its default one
- the WC is categorized with 1 category that has both US and French versions
- the user's display locale is FR
- the user searches for the french title of the category

---> Summary's locale should be French, not English

Note:
We should use the defaultLocale to avoid empty summaries when there is no translation available on the current display locale but there are matches in the category titles
LPS-48695 Add the localized assetCategoryTitles fields (not just the default, non-localized one = without locale postfix) to the search queries as keywords, otherwise users don't get results for searches for the localized category titles from the admin search boxes

FacetedSearcher already adds it.
LPS-48695 Indicate on the Search portlet's UI that the result comes from a different locale than the user's current display locale (like we do in WC Search portlet)
LPS-48695 Apply the new message to the language flag image in WC Search portlet
LPS-48695 Makes consistent
LPS-48695 We should show the message for all the assets with different language
LPS-48695 Makes the code more clear
LPS-48695 Available languageIds is no needed
LPS-48695 Show the category title and asset with the same locale
LPS-48695 Set the themeDisplayLocale as default when we don't have a locale
LPS-48695 More clean up on JAI#doGetSummary
LPS-48695 Add back default field
LPS-48695 SF
LPS-48695 Lang keys