…t in DB

Workaround T193271 performance regression by letting extensions signal that a
particular message key cannot exist in the DB. This allows us to use a
MessageCache::get hook handler to dynamically handle problematic keys in one
place (MessageCachePerformance extension) without patching core, while
maintaining compatibility with conditional message lookups that trigger fallback
logic depending on the outcome of a Message::exists() existence check.

Hooks allows to modify cache options, before user is loaded. This can be used to pass additional `checkKeys`, which will refresh user if those changed.

…eExternalImage method

Currently `Parser` allows only hot linking images with ``.jpg|.jpeg|.png|.gif` in the end of url. As we use revision, version and query params in our Vignette urls, so they would not be allowed for render even if domain was added to `wgAllowExternalImagesFrom`. `ParserAllowExternalImage` hook will be used only if domain in image url is added to `wgAllowExternalImagesFrom` list or `wgAllowExternalImages` is set to `true`.

MediaWiki only supports 14 character timestamps, and most date input
fields accordingly limit the accepted input range to fit within that
constraint, so the largest acceptable date is 9999-12-31 23:59:59.
However, if an user's own timezone preference is set to a timezone with
a higher offset than the server timezone, such dates may overflow into
the year 10000 and cause an error ("The timestamp XYZ should have 14
characters"). This very commonly happens when an admin decides to block
an user until 9999-12-31 instead of using the infinite expiry for some
reason, effectively breaking the block log for every user with a
timezone offset higher than the server offset.

Making MediaWiki support dates beyond the year 10000 would be a larger
undertaking, so for now, limit the impact of this problem by ensuring
that userAdjust() does not generate a local date that sprintfDate()
would not be able to handle.

purgeCache() invalidates the global check key for MessageBlobStore,
which results in MessageBlobStore being emptied every minute due to
wiki creations or site-wide update.php runs. Disable it while we consult
with upstream on the best way forward.

Cherry picks from REL1_37-Fandom

Upstream REL1_39 Sync

These changes need to be backported to upstream.

PLATFORM-7823 Fix SiteStats warnings

Changes:
- List view as subpage of Special:EditWatchlist so this also
shows up as a tabs
- Use skin option to determine whether to output the links in
skins that do not support sub pages

Bug: T316818
Change-Id: I1cee39c72cd0a49f97c3bdf41e07a4748502b1e2

Update REL1_39 branch

…dom-watchlist

[Cherry-pick] Watchlist: Register existing sub menu as associated pages

Sorting of the original query is not very optimized and is very slow to run because is done by the rev_id which besides unique index don't have other indexes that would optimize this query. `revactor_rev` has proper index that allows sorting the index. Therefore, reversing the query makes on DB like Marvel the process ~6x quicker and is probably even more significant for larger Databases.

Original code result:
```
Completed merge of revision_actor into the revision table, 10000 rows updated.

real    1m18.585s
user    0m2.647s
sys     0m0.757s
```

Code with the reversed query:
```
Completed merge of revision_actor into the revision table, 10000 rows updated.

real    0m15.776s
user    0m2.228s
sys     0m1.153s
```

Reverse the query in migrateRevisionActorTemp.php

Mediawiki version bump

Rendering UserLinks or Tags, requires parsing which when run on thousands of records, adds up to significant amount of processing time. More often then not, this can be optimized by storing already visited tags or user links as those "renders" will not change for the single request run but are repeated constantly on the list.

…'t allow (user is anon)

UGC-4161 | Allow section edit links when no restrictions and user can…

For anonymous users, the user ID is always zero, so it is possible for cached user links to be reused for different anonymous users after baf5c0a. This is not what we want, so use the user name as the cache key instead, which should be unique for both anonymous and registered users.

MAIN-28662 | Vary RC user(talk) link cache on user name rather than ID

PLATFORM-8338 | Add additional caching to the ChangeList rendering

MediaWiki 1.39.4 version

…es (#86)

Bug: T312169
Change-Id: I4606b4214d40596a1959bb4c4d93fb78ca9d8265

When a user saves current filter settings, the "apply" button's
message toggles whether the filter is marked as "default" or not.
As per the ticket, the message should always remain the same.

The width of the popup also changed to be wider to accommodate
a slightly longer title and the toggle of the "apply" button
width with the default icon.

Bug: T217304
Change-Id: Iee76cb422cbb011e89dd69d2feb0e74b30b2452c

PLATFORM-8107 | Fix RC filter bookmark popup rendering