Update: fix indent behavior on template literal arguments (fixes #9061)

[not-an-aardvark]

What is the purpose of this pull request? (put an "X" next to item)

[x] Bug fix (#9061)

What changes did you make? (Give an overview)

This updates the indent rule to handle multiline template arguments correctly to fix the issue described in #9061.

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

Nothing in particular

[not-an-aardvark]

This addition was necessary due to JSX behavior. When parsing code like this:

<a>
    <b>
    </b>
</a>

There is a hidden JSXText (or Literal) token between <a> and <b>, containing a newline followed by whitespace. The indent rule had previously been relying on the old template literal behavior to ensure that the <b> tag would get indented properly.

In other words, the indent rule would previously indent the above code in effectively the same manner as the below code:

a(`
    `, { // (this object is like the `b` tag)
    }, `
`);

However, by fixing this bug it would no longer possible to treat the two pieces of code in the same way anymore. The fix is to modify the token collapsing behavior (which checks whether two tokens are on the same line) to consider two tokens to be on separate lines if the second token starts with a newline character.