Breaks BrighterScript regex literal on return statment

starting code examples:

function getRegex() as dynamic
	regex = /([\xA9\xAE\x{2000}-\x{3300}\x{1F000}-\x{1FBFF}])/gmi
	return regex
end function

function getRegex() as dynamic
	return /([\xA9\xAE\x{2000}-\x{3300}\x{1F000}-\x{1FBFF}])/gmi
end function

after formatting:

function getRegex() as dynamic
	regex = /([\xA9\xAE\x{2000}-\x{3300}\x{1F000}-\x{1FBFF}])/gmi
	return regex
end function

function getRegex() as dynamic
	return / ([ \ xA9 \ xAE \ x{ 2000 } - \ x{ 3300 } \ x{ 1F000 } - \ x{ 1FBFF }]) / gmi
end function

As you can see the second functions regex is mutated after formatting.

Reproduce the formatter output using the two BrighterScript examples in the issue, then trace how a regex literal is handled when it appears directly after return. Done means formatting preserves the second function's regex exactly rather than inserting spaces or changing its escapes.