feat: replaces 'check_only' with 'dry_run' option

[jpower432]

Description

Adds a dry run option, and sets output based on the information. Add the BotResults data class to make results easier to process as an input and output to multiple classes. Adds basic results reporting to make sure that the output is readable.

Related changes are in scope of the issue, but in different commits.

• Add dry run option/remove check only
• Add reporting with the additional results
• Adds CI specific reporting for easier to read output (Changes can end up being a lot of information and it would need to collapse by default to ensure the logging output is still clear)

Fixes #181

Note: The release notes will require steps on how to migrate from check_only to dry_run.

Rationale

Failure upon diff doesn't make sense outside of the scope of auto-sync. This removes that and shifts the decision to fail to the user.

Use cases

• Receiving change from forks that should not interact with the remote repository
• Validation that the changes pass requirements before transformation on push

Type of change

• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How has this been tested?

• Unit testing
• Integration testing GitHub
  • Passing - https://github.com/jpower432/cautious-potato/actions/runs/8396695850/job/22999625816
  • Failing - https://github.com/jpower432/cautious-potato/actions/runs/8397106713/job/22999820580
  • With PR - https://github.com/jpower432/cautious-potato/actions/runs/8420708801/job/23055970558
• Integration testing GitLab
• Regression testing - Update cc-1.md jpower432/cautious-potato#152

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[beatrizmcouto]

Reviewed during paired code review. Demonstrated during the meeting