Adding a Reusable Confirmation Prompt Helper

[ProfessorSen0]

Description

Added a simple reusable confirmation so that destructive CLI commands share the same prompt behaviour.

Related Issue

Fixes #209

Type of Change

• Bug fix
• New feature
• Refactoring / CI / Docs
• Other

How to Test

cargo test confirmation

Checklist

• Code follows project style (cargo fmt + cargo clippy)
• Tests added/updated and passing (cargo test)
• Documentation updated (if applicable)

[Jordan231111]

I pushed a follow-up fix to keep this within issue #209’s scope while making it production-ready.

Problems in the original version:

• cargo clippy --all-targets --all-features -- -D warnings failed because parse_answer lived after the test module.
• The helper was not exposed through the shared utils surface, so it was not actually reusable by the future remove/restore handlers this issue is meant to support.
• The Force(pub bool) wrapper added complexity without improving call sites.
• The tests mostly exercised the parser in isolation, not the real prompt path or error handling.

Fixes applied:

• Simplified the API to confirm(prompt, force: bool).
• Kept the prompt logic injectable internally so the real confirmation path is testable without touching global stdin/stdout.
• Re-exported the helper from utils so the future CLI handlers can consume it via the intended shared-helper surface.
• Added focused tests for accepted answers, safe default-no behavior, force bypass, and write-error propagation.
• Reformatted and reran the full strict validation plus the PR-specific review commands.

Validation run after the fix:

• ./scripts/validate_strict.sh .review-commands.txt
• Included baseline fmt/clippy/all-target/all-features tests, ignored tests, doctests, cargo test confirmation, and the relevant CLI help/argument checks for remove/remove-file/restore.

With those fixes in place, this is now a clean, low-risk helper change that fits the repo’s current roadmap boundaries.