Keep file and line on compiled string range endpoints - #9848

Follow-up to @headius's review on #9838.

As far as I can tell, the file on a string literal's FrozenString is always filled in from the scope, and #9838 fixed the one place that wasn't. What's debug-only is the runtime side, which uses the file and line to say where a frozen string was created when you modify it under --debug=frozen-string-literal. That works for string range endpoints in the interpreter, but compiled code dropped the location:

def rng = ("a".."z")
rng.begin << "!"
# interpreter: can't modify frozen String, created at t.rb:1
# JIT and AOT: can't modify frozen String: "a"

The Range operand already has the file and line on both endpoints, so this passes them through ValueCompiler#pushRange to RangeObjectSite for invokedynamic and to newFrozenStringFromRaw for AOT. Each endpoint keeps its own line, in case the range spans lines. Without the debug flag, newFrozenString ignores the file and line, so nothing changes there.

The new spec puts the endpoints on separate lines and checks that both messages include where they were created. It fails in JIT and AOT mode before this change and passes in all four modes after it. The full compiler spec passes with and without invokedynamic.