🌱 Logic extraction refactor

[abrugaro]

This PR is an initial refactor and a continuation of the discussion in PR #372 and Issue #249 .

In this PR, I separate the properties of the analyzeCommand that are not arguments of the command itself and move them to another struct called CommandContext, also extracting the functions that do not use properties from analyzeCommand but do rely on CommandContext.

Additionally, I moved some functions that are not specific to analyzeCommand or CommandContext to the "utils" module.

For the next PR, the plan is to extract the logging functionality into a separate struct within its own package. This will allow it to be instantiated as a singleton, enabling decoupling of the logging logic from the rest of the code. Alongside this, I will also separate the constants currently defined at the beginning of analyze so that later, the providers can be moved to their own package.

[jmle]

Looks great. I think patterns are starting to emerge from the "god object" file that is analyze.go, and we are on the right direction.

[eemcmullan]

Overall, looks really good! My one ask is possibly renaming the CommandContext struct to something more analyzer-specific, e.g. AnalyzeCommandContext. That way, we can use the same logic across other subcommands if necessary. As of now, the only other subcmd is transform, but we are planning to add additional subcommand(s) for the asset generation work. I think this will help keep it more flexible.

[eemcmullan]

LGTM - thank you!