descriptions-are-capitalized improvements

[sbp-bvanb]

descriptions-are-capitalized: The description for argument syncDataProvider.dataProvider should be capitalized.\n dataProvider: DataProvider!"
It's not showing the docs that you need to update, might be even better. Also it shows line breaks in the logs

[sbp-bvanb]

Adding detail so this can be picked up without guessing. This also absorbs #9 — same root cause, that issue is closed as a duplicate.

What happens

Every collected error is printed as two lines by printDetailedErrors, where the second line is the raw source line the error was found on. Because the format string embeds a newline, logrus escapes it and renders it as a literal \n inside a quoted field, which is why the pasted output looks like this:

descriptions-are-capitalized: The description for argument `syncDataProvider.dataProvider` should be capitalized.\n  dataProvider: DataProvider!"

and, from #9:

The EntityTypeName should be sorted in alphabetical order. Expected sorting: AREA, CONTROL_MODULE, ... \n  enum EntityTypeName {"

Two separate complaints, one defect:

1. Literal \n in the log — the message is not readable.
2. The appended source line is not useful — for descriptions-are-capitalized it shows the field (dataProvider: DataProvider!) rather than the description that actually needs updating, and for the sorted-alphabetically rule it shows the type header including the trailing {.

Repro

go run cmd/graphql-linter/main.go -targetPath test/testdata/graphql/base/invalid/07-enum-values-sorted-alphabetically.graphql

Expected

• One log entry per error, no embedded newline: path:line: message.
• Source-line context is either dropped, or emitted as its own separate log entry (not concatenated into the message).
• For descriptions-are-capitalized, the reported line/content should point at the description string, not the field that follows it.

Where in the code

• internal/app/graphql-linter/application/report/report.go:122 — log.Errorf("%s:%d: %s\n %s", err.FilePath, err.LineNum, err.Message, err.LineContent). The \n %s is models.DescriptionError.LineContent.
• models.DescriptionError is defined in internal/app/graphql-linter/data/base/models/errors.go.
• The description rules populate LineContent via GetLineContent in internal/app/graphql-linter/data/base/rules/rules.go (see ReportUncapitalizedDescription around rules.go:581), and the sorted-alphabetically message is built at rules.go:241 / rules_helper.go:59 — note that one also embeds a \n in the message itself (...alphabetical order.\nExpected sorting: ...), so it needs the same treatment.

Done when

• No log entry contains a literal \n.
• internal/app/graphql-linter/application/report/report_test.go covers the single-line format.
• Component tests under test/component/ still pass (task remote:test-component).

Related: #12 (same reporting path, missing file path).