Bug: pizza generate codeowners needs to support the --tty-disable flag

[jpmcb]

Describe the bug

The codeowners generation flow now has interactive bits that could break CI/CD:

❯ ./build/pizza generate codeowners .
Config path loading from -c flag ~/.sauced.yaml
Finished processing commits for: /Users/jpmcb/workspace/opensauced/pizza-cli
Finished generating file: /Users/jpmcb/workspace/opensauced/pizza-cli/CODEOWNERS
Do you want to add these codeowners to an OpenSauced Contributor Insight? (y/n):

Adding the --tty-disable flag doesn't do anything and this wasn't implemented in #141

Providing the --tty-disable flag should ignore the interactive user flow:

❯ ./build/pizza generate codeowners . --tty-disable
Config path loading from -c flag ~/.sauced.yaml
Iterating commits for repo: /Users/jpmcb/workspace/opensauced/pizza-cli
Finished processing commits for: /Users/jpmcb/workspace/opensauced/pizza-cli
Finished generating file: /Users/jpmcb/workspace/opensauced/pizza-cli/CODEOWNERS

❯

Steps to reproduce

Run pizza generate codeowners on a repo with the --tty-disable flag and notice it still goes into interactive mode which could break CI/CD systems.

[open-sauced]

🎉 This issue has been resolved in version 1.3.1-beta.1 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[open-sauced]

🎉 This issue has been resolved in version 1.4.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀