Fix double yargs initialization in CLI profiling feature

[bhouston]

Fix Double Yargs Initialization in CLI Profiling Feature

This PR fixes an issue in PR #101 where yargs was being initialized twice in the main function. This double initialization was done to check for the profiling flag early, but it's inefficient and could cause problems.

Changes

1. Modified the performance.ts module to always collect timing data regardless of whether profiling is enabled

   • Only the reporting of the data is conditional on the profiling flag
   • This allows us to collect all timing data without needing to know if profiling is enabled upfront

2. Removed the early yargs initialization in the main function

   • Now we only initialize yargs once
   • The profiling flag is checked after yargs has been properly initialized

3. Updated tests to reflect the changes

Related Issues

Fixes part of #100 (CLI startup performance issues)
Should be merged into PR #101

Testing

All functionality of the profiling feature remains intact, but the implementation is now more efficient.

[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 📦🚀