[BUGFIX] Fix mixed up $cachingEnabled property in BootCompletedEvent

The BootCompletedEvent receives the constructor argument
`$cachingEnabled`. However, the variable `$disableCaching` was passed
in Bootstrap::init() which is the exact opposite. In fact, the caching
is logically always enabled when reaching the dispatched event.

Resolves: #103114
Releases: main, 12.4
Change-Id: I81c26027bb8e2cb4009fbfcd0bfd6015bd9c1dec
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82993
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Benni Mack <benni@typo3.org>
Tested-by: core-ci <typo3@b13.com>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: Benni Mack <benni@typo3.org>
Tested-by: Nikita Hovratov <nikita.h@live.de>
Reviewed-by: Nikita Hovratov <nikita.h@live.de>

typo3/sysext/core/Classes/Core/Bootstrap.php

@@ -154,7 +154,7 @@ public static function init(
         $GLOBALS['TCA'] = $tcaFactory->get();
         static::checkEncryptionKey();
         $bootState->complete = true;
-        $eventDispatcher->dispatch(new BootCompletedEvent($disableCaching));
+        $eventDispatcher->dispatch(new BootCompletedEvent(true));
 
         return $container;
     }