feat: dedicated coverage command

[juan-vgv]

Description

We could consider adding a new dedicated command to manage coverage in a project:

very_good coverage:

• returns success if the coverage is above a default threshold (100% I guess?)
• error if it is below

It should take the usual parameters: --min-coverage, --exclude and the newly added --collect-coverage-from.

Once the CLI can do the job on its own, we could update the Very Good Workflows to use it, and deprecate Very Good Coverage, which would simplify our stack.

To avoid breaking changes, we could set the --coverage flag in very_good test as deprecated until the next major CLI release.

Thoughts?

@omartinma is #418 the issue you were thinking about?

Requirements

• All CI/CD checks are passing.
• There is no drop in the test coverage percentage.

Additional Context

No response

[marcossevilla]

thanks for the consideration @juan-vgv!

since this is an interesting change, we're currently adding the missing features from Very Good Coverage to the very_good test command in the CLI. when we reach feature parity between the 2, we will replace Very Good Coverage usage with the CLI and then deprecate it.

updates for this deprecation will be communicated through this issue, thanks!