fix: allow JSONRuleDefinition to report on tokens

[Pixel998]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request?

This PR fixes an issue where the JSONRuleDefinition type was overly restrictive, preventing rules from reporting issues on tokens (including comments and punctuation).

Previously, the Node type parameter was set to AnyNode, which caused TypeScript errors when rules attempted to use context.report() with tokens retrieved from sourceCode.comments or node.tokens.

What changes did you make? (Give an overview)

Fixed the Node constraint in JSONRuleDefinition by changing it from AnyNode to JSONSyntaxElement.

Related Issues

Is there anything you'd like reviewers to focus on?

[lumirlumir]

Could you update the PR description to include the bug template? It will help others clearly identify the problem you're facing.

[DMartens]

@lumirlumir This would allow reporting tokens such as a comma , or an opening brace {.
For example in a rule like no-comma-dangle this would be currently not allowed:

export default {
	create(context) {
		return {
			Object(object) {
				const lastMember = object.members.at(-1);
				
				const danglingComma = sourceCode.getTokenAfter(lastMember);
				if (danglingComma !== null) {
					// The type does not allow passing a token as the `node`
					context.report({ message: 'No dangling commas', node: danglingComma });
				}
			}
		}
	}
}

[lumirlumir]

LGTM, thanks.

Would like @DMartens to verify before merging.