Taxonomy field ignores accented characters when checking if a term exists

Steps to reproduce

1. Using the ACF taxonomy term, insert a new term without using characters: e.g. Commes des Garcons
2. Then try and insert a new term with accented characters: e.g. Comme des Garçons. ACF considers them identical and won't add it.
3. The default WP taxonomy admin pages does treat the two names as different, and will let you add them both.

Admittedly, a bit of an edge case, but client ran into this issue on a site that handles a lot of accented characters. They had incorrectly spelt a term, but when they tried to correct it by adding a new term with the correct accented characters, the ACF field refused to insert it. I'm guessing it compares against the slug rather than the term name itself. While you can edit the terms using WP's default taxonomy menus, I prefer to not show those in the admin to simplify things for the end client.

Start by tracing the ACF taxonomy field's term-existence check and compare it with how the default WordPress taxonomy admin handles “Commes des Garcons” and “Comme des Garçons.” Done means distinct terms that differ only by accented characters can both be added through the ACF taxonomy field, without changing the existing behavior for genuinely identical terms.