OLS, Mediawiki, and LiteSpeedCache

Using the latest OLS with Mediawiki to try and take advantage of the [LitespeedCache extension](https://www.mediawiki.org/wiki/Extension:LiteSpeedCache), and seem to have discovered some sort of problematic interaction with scripts added via extensions or hooks that set cookies. Vanilla Mediawiki does not have this problem, according to my tests, but as soon as there's a script (like Google Analytics via [the Gtag extension](https://www.mediawiki.org/wiki/Extension:GTag) or [this hook](https://stackoverflow.com/questions/56862624/how-can-i-insert-a-google-analytics-snippet-into-my-mediawiki-wiki-pages) from the top answer at Stackoverflow) that sets a cookie, it seems that maybe ls_smartpush (maybe!) leads to some sort of inappropriate prefetching that voids efforts to cache a page. Other things hooked in -- I had meta-tags set via a hook, and a simple javascript that did not set cookies but would rewrite links to an affiliate -- did not seem to cause this problem.

Some of this is above my understanding, but from near the end of [page 3 and on on the OLS forum](https://forum.openlitespeed.org/threads/lscache-mediawiki-plugin.5918/page-3) an experienced LSWS user looked into it and found that LSWS + the LiteSpeedCache extension worked without a problem even when using Gtag, so it seems to be some sort of difference between OLS and LSWS that isn't obvious. Again, the ls_smartpush thing may be part of it, but it does not seem to be the case that smartpush can be disabled via an .htaccess directive as it can be in LSWS.

Reproduce the interaction with OpenLiteSpeed, MediaWiki, the LiteSpeedCache extension, and a cookie-setting script such as GTag. Compare the results with LiteSpeed Web Server and investigate whether ls_smartpush causes inappropriate prefetching or whether OpenLiteSpeed lacks the relevant disabling directive; done means identifying the cause and a reproducible resolution.

Written by the indexing model from the issue text.