Fix/3592 bypass non interactive flag prompts

[kperkins96]

Description

Fixes the --non-interactive flag to consistently accept all confirmations instead of using default values. Previously, when --non-interactive was used, CLI commands would still abort if a confirmation's default was False, making the flag unreliable for automation and CI/CD workflows.

Changes:

• Modified NonInteractiveAction in dlt/_workspace/cli/_dlt.py to set ALWAYS_CHOOSE_VALUE = True instead of ALWAYS_CHOOSE_DEFAULT = True
• Updated user-facing message to clarify behavior: "Confirmations are automatically accepted"
• Added comprehensive test coverage in tests/workspace/cli/test_non_interactive.py for drop, sync, and drop-pending-packages commands
• Updated tests/workspace/cli/conftest.py to properly import test fixtures

Behavior:

• Before: --non-interactive would use the default answer for each prompt (could be True or False)
• After: --non-interactive always accepts confirmations (True), allowing commands to proceed without user interaction

This makes the flag reliable for CI/CD pipelines and automated scripts where prompts cannot be answered interactively.

Related Issues

• Fixes The --non-interactive flag appears to default to “No” for prompt confirmations #3592

Additional Context

Testing:

• Added test_non_interactive.py
• New tests use echo.always_choose(False, True) context manager to simulate --non-interactive behavior
• Ran make format && make lint - all checks pass
• Ran make test-workspace - all tests pass

Implementation notes:

• The fix leverages the existing ALWAYS_CHOOSE_VALUE in echo.py
• When set to True, confirm() and prompt() return True instead of prompting the user
• The --non-interactive flag only affects behavior when explicitly used - no changes to default CLI behavior

[anuunchin]

Thanks for the PR!

Changing --non-interactive from "use defaults" to "always accept" is a breaking change. Anyone currently using --non-interactive in CI scripts may be relying on destructive commands being safely skipped - which makes sense imo

How about adding a separate --yes / -y flag that sets ALWAYS_CHOOSE_VALUE = True, while leaving --non-interactive unchanged? That would address the reported issue and just be an additive change

[kperkins96]

Added a new --yes / -y flag that automatically accepts all confirmations without prompting and preserved existing --non-interactive behavior.

Changes:

• Added new YesAction class in dlt/_workspace/cli/_dlt.py that sets ALWAYS_CHOOSE_VALUE = True
• Added --yes / -y argument to the CLI parser
• --non-interactive remains unchanged (uses ALWAYS_CHOOSE_DEFAULT = True)
• Added test coverage in tests/workspace/cli/test_yes_flag.py

Behavior:

• --non-interactive (unchanged): Uses each prompt's default value (safe for existing scripts)
• --yes / -y (new): Always accepts confirmations, allowing commands to proceed without interaction

[kperkins96]

@anuunchin do you mind taking another look when you get a chance? Thanks!