no-implicit-coercion does not check template literals

[kaicataldo]

The version of ESLint you are using
Master

The problem you want to solve.
While working on #7060 I noticed that no-implicit-coercion does not check for implicit coercion using template literals. While this isn't a common practice, I think we should add it for the sake of completeness.

Your take on the correct solution to problem.
no-implicit-coercion should warn when it finds the following patterns:

`` + foo; // Error: use `String(foo)` instead.
foo + ``; //  Error: use `String(foo)` instead.
foo += ``; // Error: use `foo = String(foo)` instead.

I have a local branch with an implementation and tests and am happy to make a PR once #7060 has been merged.

[platinumazure]

👍 from me.

[vitorbal]

👍!!

[kaicataldo]

@eslint/eslint-team Any other thoughts on this? Could use one more supporter/would love to hear any arguments against.

[mikesherov]

It's a bug if it's not checking Template Literals. Should probably also check tagged template literals too.

👍

[mikesherov]

Err, I guess not for tagged template expressions because those could return non strings. Nvm.

[ilyavolodin]

👍

[kaicataldo]

Thanks all - I'll put together a PR