fix(cli): cleanup message for input with no config

[escapedcat]

Description

Avoid confusing duplication of result message if input and empty config.
As discussed on slack.

Usage examples

Somewhere outside of the repo try:

echo "null " | node commitlint/@commitlint/cli/lib/cli.js --config commitlint/@commitlint/cli/fixtures/empty/commitlint.config.js

Result before:

⧗   input: null
✔   found 0 problems, 0 warnings
    (Need help? -> https://github.com/marionebl/commitlint#what-is-commitlint)
✖   Please add rules to your `commitlint.config.js`
    - Getting started guide: https://git.io/fpUzJ
    - Example config: https://git.io/fpUzm [empty-rules]
✖   found 1 problems, 0 warnings
    (Need help? -> https://github.com/marionebl/commitlint#what-is-commitlint)

Result after:

⧗   input:
null

✖   Please add rules to your `commitlint.config.js`
    - Getting started guide: https://git.io/fpUzJ
    - Example config: https://git.io/fpUzm [empty-rules]
✖   found 1 problems, 0 warnings
    (Need help? -> https://github.com/marionebl/commitlint#what-is-commitlint)

How Has This Been Tested?

Has not.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[escapedcat]

I think I need to check for the weird line-break after ⧗ input: now...

[byCedric]

I think I need to check for the weird line-break after ⧗ input: now...

I think there might be something going on in the formatter itself, because the whole format is being structured in that module. Maybe we should trim this line or something like that?

[marionebl]

Sorry the review took me so long. LGTM!