add interactive flag

[davidgamero]

Description

In order to better serve automated and batch workflows, as well as the wrapped-binary consumption patter, i propose adding a new interactive flag that will error on stderr instead of interactively prompting.

this will open up automation options like running in github actions with better error handing

Fixes # (issue)
Feature # (details)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Refactor

How Has This Been Tested?

Provide instructions so we can reproduce, and list any relevant details for your test configuration. Please mention if this is a breaking change which will impact consuming tool(s).

• Unit Test:
• E2E Test:
• Other Test:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[ReinierCC]

Looks good.

[Tatsinnit]

❤️ Thank you so much for the ping and these changes, beside a minor suggestion looks great! We can always do extractions of string to more common place config way latter.