fix: melos list --cycles should return error exit code for easier integration with CI pipelines

[mugbug]

Is there an existing issue for this?

• I have searched the existing issues.

Version

3.0.1

Description

When melos list --cycles is called and some cycle is found it means something is wrong with the project and we should return an error code to the terminal, but we currently just log an output message with the error information.

Steps to reproduce

1. Go to a project with multiple repos
2. Make sure two packages are referencing each other
3. Run melos list --cycles

Expected behavior

An exit code != 0 to be returned from the CLI.

Screenshots

No response

Additional context and comments

This should be specially useful when calling this command on a CI workflow. By having an exit code != 0, it should be enough to just call this command on the workflow and it will fail if any cycle is detected. Without this change, to add it to a CI workflow, an output check should be added to check if the expected output string was found or not, which is not really ideal since the output string may change without being considered as breaking change.