Output is implementation focused, not human focused

[epage]

Describe your use case

I ran cargo semver-checks on my project (#296) and had a hard time looking through the results

• Issues related to an API item were scattered by which check they fell into
• I could easily skim the results to find something I was looking for because they were organized by check
• The most relevant details don't stand out and are lost in the noise

Describe the solution you'd like

• Sort the lints by one of
  • (idea) API path, file, line, check
  • file, line, check
• Format each message in a more traditional diagnostic format, whether brief or long

Alternatives, if applicable

No response

Additional Context

No response