[flake8-type-checking] Fix some safe fixes being labeled unsafe

[Daverball]

Summary

We were mistakenly using CommentRanges::has_comments to determine whether our edits
were safe, which sometimes expands the checked range to the end of a line. But in order to
determine safety we need to check exactly the range we're replacing.

This bug affected the rules runtime-cast-value (TC006) and quoted-type-alias (TC008)
although it was very unlikely to be hit for TC006 and for TC008 we never hit it because we
were checking the wrong expression.

Test Plan

cargo nextest run

[Daverball]

I disovered this bug while working on #15635

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

[MichaReiser]

Thank you. Yeah, has_comments is somewhat misleading. It tries to do the right thing but its name is too generic. I think it's mainly optimized for testing if a statement (possibly compound) has any comments but it is to forgiving in that case...