fix(js_formatter): updated the is_test_call_expression function to match prettier

[mdm317]

Summary

fixes #4202

https://github.com/prettier/prettier/blob/d9d0999aac70c04b06b35cbcb2c804b4a9c8d8a8/src/language-js/utils/index.js#L383-L387

For Prettier, assume it is a Testcall only if the first argument is a StringLiteral or TemplateLiteral.
So, I added the logic.
However, assuming that it is not a Testcall if the first argument is neither a StringLiteral nor a TemplateLiteral might have some edge cases.
Please share your thoughts.

Test Plan

add test

[codspeed-hq]

CodSpeed Performance Report

Merging #4811 will not alter performance

_{Comparing mdm317:fix/4202 (beba389) with main (a658a29)}

Summary

✅ 95 untouched benchmarks

[mdm317]

in ci

error: test failed, to rerun pass -p biome_js_formatter --test prettier_tests

I don't understand why this error occurs, even though the issue-4202.js.prettier-snap file exists.
Can someone help me?

[dyc3]

The tests in specs/prettier are synced with the prettier repo. You should move your new snapshot tests outside of that folder into specs/js.

[ematipico]

@mdm317 Also, you should add template literals to the tests, since they are part of the new logic

[mdm317]

@dyc3
Thank you for letting me know. It was really helpful!

@ematipico
Thank you for the review. I have one question.

biome/crates/biome_js_formatter/tests/specs/prettier/js/test-declarations/test_declarations.js.prettier-snap

Lines 19 to 21 in a658a29

	it(`does something really long and complicated so I have to write a very long name for the test`, function () {
	console.log("hello!");
	});

Template literals are already exist, and the results won't change.
Should I still add them?
If I misunderstood something, please let me know.

[ematipico]

@mdm317 can you please add another test case with template literals?