feat: add non-interactive session checking to modern commands

[paulbalandan]

Description
Adds a non-interactive session capability to the modern AbstractCommand framework introduced in #10120. Previously interact() always fired, so modern commands could hang on CLI::prompt() when run in CI, cron, or piped contexts.

This PR adds:

• A reserved default option on every modern command: --no-interaction / -N.
• Public API on AbstractCommand: isInteractive(): bool and setInteractive(bool): static.
• Precedence: explicit setter > CLI flag > STDIN TTY detection.
• Automatic cascade of the non-interactive state to sub-commands invoked via $this->call(...); a caller-supplied flag wins over propagation.
• A new ?bool $noInteractionOverride parameter on call(): null (default) propagates, true forces non-interactive, false strips any inherited --no-interaction so the child resolves its own state.
• logs:clear now shows its --force hint only in non-interactive mode, resolving an existing @todo.

Note
The shortcut is -N (capital) rather than -n because several legacy migration commands: migrate, migrate:refresh, migrate:rollback already use -n as the shortcut for --namespace. Capital -N leaves that shortcut free if any of those commands are later migrated to AbstractCommand.

Checklist:

• Securely signed commits
• Component(s) with PHPDoc blocks, only if necessary or adds value (without duplication)
• Unit testing, with >80% coverage
• User guide updated
• Conforms to style guide

[michalsn]

Looks solid - nice work

[Copilot]

Pull request overview

Adds a first-class non-interactive mode to CodeIgniter’s modern AbstractCommand CLI framework so commands don’t hang on prompts in CI/cron/piped executions, and propagates that state through sub-command calls.

Changes:

• Injects a default --no-interaction / -N option into all modern commands and skips interact() when non-interactive.
• Adds AbstractCommand::isInteractive() / setInteractive() plus interactive-state propagation semantics for $this->call(..., ?bool $noInteractionOverride).
• Updates docs/changelog and expands system tests (including logs:clear behavior) to cover the new mode.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
user_guide_src/source/cli/cli_modern_commands.rst	Documents --no-interaction, interactive state precedence, and call() propagation/override semantics.
user_guide_src/source/changelogs/v4.8.0.rst	Adds changelog entry describing the new flag and APIs.
system/CLI/AbstractCommand.php	Implements interactive-state tracking, default option injection, call() override param, and propagation logic.
system/Commands/Housekeeping/ClearLogs.php	Adjusts abort messaging to show the --force hint only in non-interactive mode.
tests/system/CLI/AbstractCommandTest.php	Adds coverage for skipping interact(), isInteractive() behavior, and call() propagation/override cases.
tests/system/Commands/Housekeeping/ClearLogsTest.php	Adds data-driven test verifying non-interactive abort output includes the --force hint.
tests/system/Commands/HelpCommandTest.php	Updates expected help output to include -N, --no-interaction.
tests/_support/Commands/Modern/InteractiveStateProbeCommand.php	New fixture command to record whether interact() ran and what interactive state was observed.
tests/_support/Commands/Modern/ParentCallsInteractFixtureCommand.php	New fixture command to exercise call() interactive propagation and override behavior.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[michalsn]

I think we can "leak" the interactive state across repeated run() calls on the same command instance. This is not a problem for normal command usage, so I'm not sure if we should bother... although it can affect tests or other code that manually reuses a command object, like:

$cmd = new MyCommand();
$cmd->run([], ['no-interaction' => null]);
$cmd->run([], []);

[paulbalandan]

Fixed. The flag becomes a per-run switch. Only setInteractive() call is persistent across runs.