bug: inline config errors are misleading

[DaniPopes]

another thing is that line is documented and interpreted as {line}:{column}:{length}, but is in fact {byte_start}:{byte_end}:{source_id} in both parsers. This should be fixed in another PR

Originally posted by @DaniPopes in #9615 (comment)

This refers to when inline config errors are printed like {path}:1:2:3, the 1:2:3 should be {line}:{column} but is instead something else