Standardize nullable type hints to 'null|Type' order

Refactors type hints and docblocks across the codebase to consistently use the 'null|Type' order for nullable types, improving code readability and alignment with modern PHP standards. No functional changes are introduced; this is a documentation and type annotation update only.

Author: huangdijia

src/View/Components/Choice.php

@@ -21,7 +21,7 @@ class Choice extends Component
      * @param string $question
      * @param array<array-key, string> $choices
      * @param mixed $default
-     * @param mixed|null $attempts
+     * @param null|mixed $attempts
      * @param mixed $multiple
      * @return mixed
      */

src/View/Components/Task.php

@@ -22,7 +22,7 @@ class Task extends Component
      * Renders the component using the given arguments.
      *
      * @param string $description
-     * @param (callable(): bool)|null $task
+     * @param null|(callable(): bool) $task
      * @param int $verbosity
      */
     public function render($description, $task = null, $verbosity = OutputInterface::VERBOSITY_NORMAL)

src/View/Components/TwoColumnDetail.php

@@ -19,7 +19,7 @@ class TwoColumnDetail extends Component
      * Renders the component using the given arguments.
      *
      * @param string $first
-     * @param string|null $second
+     * @param null|string $second
      * @param int $verbosity
      */
     public function render($first, $second = null, $verbosity = OutputInterface::VERBOSITY_NORMAL)