[TASK] Improve some type annotations in TypoScript-related classes

Resolves: #99148
Releases: main
Change-Id: I7bef875aefaf82a5183c7d8c2b7c626b97b7eb2c
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/76754


Reviewed-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: Stefan Bürk <stefan@buerk.tech>
Reviewed-by: Stefan Bürk <stefan@buerk.tech>
Tested-by: Christian Kuhn <lolli@schwarzbu.ch>
Tested-by: core-ci <typo3@b13.com>

typo3/sysext/core/Classes/TypoScript/AST/Node/RootNode.php

@@ -73,6 +73,9 @@ final class RootNode extends AbstractNode
         return true;
     }
 
+    /**
+     * @return array<string, mixed>
+     */
     public function toArray(): array
     {
         $result = [];

typo3/sysext/core/Classes/TypoScript/TypoScriptService.php

@@ -31,8 +31,8 @@ class TypoScriptService
      * Extbase converts the "classical" TypoScript (with trailing dot) to a format without trailing dot,
      * to be more future-proof and not to have any conflicts with Fluid object accessor syntax.
      *
-     * @param array $typoScriptArray The TypoScript array (e.g. array('foo' => 'TEXT', 'foo.' => array('bar' => 'baz')))
-     * @return array e.g. array('foo' => array('_typoScriptNodeValue' => 'TEXT', 'bar' => 'baz'))
+     * @param array<string|int, mixed> $typoScriptArray for example `['foo' => 'TEXT', 'foo.' => ['bar' => 'baz']]`
+     * @return array<string|int, mixed> for example `['foo' => ['_typoScriptNodeValue' => 'TEXT', 'bar' => 'baz']]`
      * @internal Avoid using this method. This has been invented for Extbase, which decided to move TypoScript
      *           arrays around in just another different way.
      * @todo: Usages should be removed mid-term to work on the TypoScript object tree directly.