Lataa Config File Validator 2.1.0

SARIF Inline Annotations
- SARIF reporter now emits region with startLine/startColumn on each result, enabling GitHub Actions to post inline PR annotations on the affected lines
- 10 validators return structured position info (JSON, YAML, TOML, XML, HCL, CSV, ENV, HOCON, TOON, PList)
- 4 validators without position info (INI, EditorConfig, Properties, SARIF) fall back to file-level annotations
- Added ValidationError type with optional Line/Column fields
Multi-Error Separation
Previously, multiple schema validation errors were joined into a single string. Each reporter now handles them individually:
- Standard: each error on its own indented line
- JSON: "errors" array instead of a single "error" string
- SARIF: each error as its own result entry (one annotation per error)
- JUnit: each error on its own line within the <failure> message
Added SchemaErrors type to carry individual error messages from JSONSchemaValidate, ValidateXSD, and SARIF schema validation.
Error Type Classification
- All errors are prefixed with syntax: or schema: across every reporter
- New -groupby error-type option groups output into syntax, schema, and Passed categories
- Works with all existing groupby combinations (e.g. -groupby error-type,filetype)
XSD Error Improvements
- XSD validation now reports detailed diagnostics via helium ErrorCollector instead of the generic "xsd: validation failed"
- Error format cleaned up from (string):5: Schemas validity error : ... to line 5: ...
Documentation
- Added GitHub Action section to README and index referencing Boeing/validate-configs-action@v2.0.0
- Updated groupby documentation to include error-type
- Updated CHANGELOG for 2.1.0