Support multiple output formats for violation reporting

[raffaelecarelle]

Added support for violation reporting in both text and JSON formats by introducing a Printer interface and implementing TextPrinter and JsonPrinter classes. Refactored relevant methods to utilize the new Printer system and updated CLI options to allow format selection. Included comprehensive unit tests for the new functionality.

[micheleorselli]

It looks good to me, just out of curiosity: is there a particular use case for the json output?

[raffaelecarelle]

Hi @micheleorselli, for me the scope of the feature is to use with gitlab ci and code quality format supported is json.

https://docs.gitlab.com/ci/testing/code_quality/#import-code-quality-results-from-a-cicd-job

thank you

[micheleorselli]

Hey @raffaelecarelle, before merging would you mind:

1. moving the Printer directory under the CLI one?
2. add an e2e test here to check the new option --format=json ?

Thanks 🙇

[raffaelecarelle]

Hey @raffaelecarelle, before merging would you mind:

1. moving the `Printer` directory under the `CLI` one?

2. add an e2e test [here](https://github.com/phparkitect/arkitect/blob/main/tests/E2E/Cli/CheckCommandTest.php) to check the new option `--format=json `?

Thanks 🙇

Hi, I realized that in order to have a valid json, it is necessary to suppress all irrelevant output. So I added another optione --only-errors to do this!

As you suggested then, I added an e2e and moved the printer under the CLI folder.

Let me know.

[micheleorselli]

my 2 cent: it feels a bit strange having to specify two options in order to get the right output. it would be nice that if I specify --format=json then I only get json as output, no additional option needed
@AlessandroMinoccheri @fain182 wdyt?

[raffaelecarelle]

I too initially thought this but preferred to add an option for clarity and greater flexibility. Anyway you tell me, no problem with unifying.

[fain182]

I think that to make the --format=json option easier to use, we should ensure it automatically includes the behavior of --only-errors. And if we can't think of any use cases for using --only-errors on its own, I’d suggest removing it.

So I agree with you @micheleorselli

[raffaelecarelle]

ok guys, I remove the --only-errors option.

As you said, this make easier option json to use.

ps if other format will added (ex XML), is enought to add it in this condition

 $onlyErrors = Printer::FORMAT_JSON === $format;

[micheleorselli]

thanks @raffaelecarelle!