New rule `require-error-positions`

[FloEdelmann]

Many contributors add tests with only line: 4 for reported errors. Often, the test cases should include the column and end position though. This could be enforced with a new ESLint rule that requires all of line, endLine, column, and endColumn to be present for all expected errors.

[aladdin-add]

Currently, there is no rule enforcing the structure of error objects. I am considering introducing a rule that developers can configure to enforce which properties (such as line, endLine, column, and endColumn) must be present in error objects. Additionally, this rule could specify whether the properties must follow a certain order. Of course, this will require a more detailed and specific design.

[StyleShit]

configure to enforce which properties must be present

well, I think this would be pretty verbose in some cases. Maybe it could have some predefined presets?

roughly something like this:

'consistent-test-errors-structure': ['error', {
	presets: [ 'error-positions' ] 
	includeKeys: [ 'messageId' ],
	excludeKeys: [ 'type' ],
	order: [ 'messageId', 'line', 'endLine', 'column', 'endColumn', 'suggestions'],
} ]

[DMartens]

The feature to require error positions and enforce using either messageId or message will soon land in the rule tester (RFC, PR).

[StyleShit]

Seems like it has landed @DMartens, so this issue can be closed

(Personally, I would prefer getting this error in my IDE rather than much later, when running tests)