`begin` matching ending `\n` creates rogue `\\G` on every newline

A begin/end rule will create a \\G anchor immediately after the begin match ✅

however, if the begin rule matches the ending newline \n character
it causes it to place a \\G anchor at the beginning of every single line within the begin/end rule ❌

create a grammar with the following code

"begin": "#\n",
"end": "#",
"patterns": [
	{
		"match": "\\G.",
		"name": "invalid"
	}
]

create a file and apply the grammar

#
ab
cd
#

notice how both a and c are highlighted red ❌

even tho there should not be any \\G anchors there

remove the \n newline from the grammar
notice that there is now no incorrect \\G anchors ✅

TextMate Help/TextMate.md states:

\G matches end of parent rule’s begin — or end of last stacked while.

Reproduce the issue with the supplied TextMate grammar and four-line file, then trace the begin/end tokenization path that inserts the \G anchor after a begin match. Done means the newline-ending begin rule no longer causes \G to match at the start of each line, while the documented behavior remains intact.