Add `init` command

[roxblnfk]

The command should create default config

[burn1ngbear]

Title

Add interactive testo init command for automatic project setup

Description

Implement the vendor/bin/testo init (or testo init) command that allows users to quickly set up the test environment without manually copying configuration from the documentation. The command should analyze the existing project structure, ask a minimum number of questions, and generate the configuration file.

Main Requirements

1. Command

   • Add a new init command (no extra flags).
   • Invocation: vendor/bin/testo init

2. Auto-detection of project structure

   • Check for the existence of a src/ folder. If it exists, do not ask the user about the source code location.
   • If src/ is missing, ask the user for the source directory path (e.g., lib/, app/, etc.).
   • Check for a tests/ folder:
     • If the folder is missing or empty – suggest creating a standard test structure (see item 3).
     • If tests/ already contains subdirectories (e.g., Unit/, Functional/), recognize them and use them without asking unnecessary questions.

3. Test type configuration

   • By default, suggest standard paths:
     • Unit tests: tests/Unit
     • Functional tests: tests/Functional
   • If the user wishes to change the paths, allow them to specify custom ones.
   • Questions should only be asked when suitable directories cannot be auto-detected.

4. Configuration file generation

   • Generate a configuration file (presumably testo.php) based on the collected data.
   • If the file already exists – warn the user and ask whether to overwrite or exit.

5. Composer integration (optional)

   • Suggest adding a test script to composer.json (e.g., "test": "testo").
   • Ask the user if they want this.

6. Final output

   • After successful creation, display a message including:
     • Path to the created configuration file.
     • Command to run tests: vendor/bin/testo.
     • Link to documentation: https://php-testo.github.io/docs/intro/getting-started

Definition of Done

• The testo init command is implemented and works.
• The command correctly detects the presence/absence of src/ and tests/.
• Interactive mode asks the minimum number of questions, leveraging auto-detection.
• A valid configuration file is created (structure according to current Testo requirements).
• When appropriate, the user is prompted to add a script to composer.json.
• A clear instruction message is printed for the user.
• Tests for the new command are written (unit + integration).
• Documentation is updated (description of the init command).

Additional Notes

• The main goal is to minimize user actions. The more auto-detection, the better.
• In case of ambiguity (e.g., multiple possible test directories), ask a single clarifying question instead of many.
• The command must be safe: do not delete existing files without explicit user consent.