feat: add CLI options for automated usage scenarios

[bhouston]

Summary

This PR adds two new CLI options to support automated usage scenarios:

• --userWarning=false - Disables the user consent check
• --upgradeCheck=false - Disables the version upgrade check

Problem

When running MyCoder in automated environments like CI/CD pipelines:

1. The user consent prompt blocks execution and requires manual intervention
2. The version upgrade check adds unnecessary output and network calls

Solution

Added two boolean CLI options that can be set to false to disable these features:

• --userWarning=false bypasses the consent check
• --upgradeCheck=false skips the version check

Changes

• Added new options to SharedOptions type and sharedOptions object in options.ts
• Updated consent check in .ts to respect the userWarning option
• Updated version check in .ts to respect the upgradeCheck option
• Updated documentation in README files

[bhouston]

I've updated the implementation of --userWarning=false to just skip the consent check without saving consent. This follows standard UX conventions where boolean flags should not cause permanent side effects. The option now just bypasses the check for the current session.

[github-actions]

🎉 This PR is included in version 0.9.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version mycoder-v1.0.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀