feat: Add -y / --yes flag for non-interactive CI/CD execution

[bolespolo4]

👋 Hey everyone!

I'd love to start a conversation about adding a non-interactive execution
mode to flutter_flavorizr — specifically a -y / --yes flag.

---

🔍 Context

Many Flutter teams are adopting automated pipelines (GitHub Actions, Bitrise,
Codemagic, etc.) and want to include flutter_flavorizr as a step in those
pipelines. The current interactive prompt model blocks this completely since
there is no user available to respond during CI runs.

---

💡 The Idea

Add a -y / --yes flag to the CLI that:

• Bypasses all interactive prompts with safe defaults
• Keeps existing behavior 100% intact when the flag is not used
• Makes the tool usable in any non-interactive environment

This follows a well-established CLI convention used by tools like:

• apt-get install -y
• npm init -y
• create-react-app --yes

---

❓ Questions for the Maintainer & Community

1. Is this something aligned with the vision of the project?
2. Should -y be a standalone flag or an extension of the existing -f flag?
3. Are there any prompts that should not be bypassed even with -y
   (e.g. destructive or irreversible operations)?
4. Any preferred implementation approach or conventions I should follow?

---

🙋 My Intent

I have already drafted the implementation scope and I am ready to open a PR.
I just want to make sure the approach is aligned before investing the time,
to avoid building something that doesn't fit the project's direction.

Happy to hear any thoughts — from the maintainer or the community! 🚀

[AngeloAvv]

Hello @bolespolo4 ! flutter_flavorizr already supports -f (or --force) param to skip interactive mode. This is already well established in the project's CI for testing a blank project. See here

Am I missing any point?