Restore original order: generate README before package installation

Reverted to the original order where README generation happens BEFORE package installation. This avoids issues with Composer's autoloader being modified by package installation and then causing problems when spawning new processes.

The flow is now:
1. Scaffold tests
2. Generate README (using wp-cli.yml to load commands)
3. Scaffold GitHub files
4. Install package (if not skipped)

This way README generation works with launch=false and --path flag, and doesn't conflict with package installation.

Co-authored-by: swissspidy <841956+swissspidy@users.noreply.github.com>

Author: Copilot

src/ScaffoldPackageCommand.php

@@ -150,17 +150,17 @@ public function package( $args, $assoc_args ) {
 			WP_CLI::runcommand( "scaffold package-tests {$package_dir} {$force_flag}", array( 'launch' => false ) );
 		}
 
+		if ( ! Utils\get_flag_value( $assoc_args, 'skip-readme' ) ) {
+			WP_CLI::runcommand( "scaffold package-readme {$package_dir} {$force_flag}", array( 'launch' => false ) );
+		}
+
 		if ( ! Utils\get_flag_value( $assoc_args, 'skip-github' ) ) {
 			WP_CLI::runcommand( "scaffold package-github {$package_dir} {$force_flag}", array( 'launch' => false ) );
 		}
 
 		if ( ! Utils\get_flag_value( $assoc_args, 'skip-install' ) ) {
 			Process::create( "composer install --working-dir {$package_dir}" )->run();
 			WP_CLI::runcommand( "package install {$package_dir}", array( 'launch' => false ) );
-
-			if ( ! Utils\get_flag_value( $assoc_args, 'skip-readme' ) ) {
-				WP_CLI::runcommand( "scaffold package-readme {$package_dir} {$force_flag}", array( 'launch' => true ) );
-			}
 		}
 
 		// Display next steps guidance for users.