Include the opening brace's line in multiline f-string errors

An unclosed f-string replacement field can report an error on a later line, making the opening brace hard to find:

var = "abc"
a = f""" {var} extern "C" { """
b = """ string """

  File "script.py", line 3
    b = """ string """
                   ^
SyntaxError: f-string: expecting '}'

The quotes after the second { start a string inside the replacement field. That string ends on line 3, and the final quotes start another string that is never closed.

The error should include the line number of the opening brace:

SyntaxError: f-string: expecting '}' to close '{' on line 2

The same problem affects t-strings. Valid strings inside replacement fields should continue to work.

Linked PRs

• gh-157779

Start with the provided multiline f-string reproducer and compare its diagnostic with the expected message. Check the corresponding t-string case and confirm that valid strings inside replacement fields still work. Done means both affected error messages identify the opening brace's line without regressing valid strings; a linked pull request is already listed.