Track ranges of names inside __all__ definitions

[AlexWaygood]

Summary

This resolves the TODO comment here:

ruff/crates/ruff_linter/src/checkers/ast/mod.rs

Lines 2116 to 2118 in 4f06d59

	// Mark anything referenced in `__all__` as used.
	// TODO(charlie): `range` here should be the range of the name in `__all__`, not
	// the range of `__all__` itself.

Fixing this TODO is necessary (though not quite sufficient) for fixing #10508.

This PR adds a new struct for representing __all__ members to crates/ruff_python_ast/all.rs:

struct DunderAllMember<'a> {
    name: &'a str,
    range: TextRange
}

I initially just kept references to ExprStringLiteral nodes around, since they have all the information we need here, but apparently that approach leads to a large performance regression 🙃

Test Plan

cargo test

[codspeed-hq]

CodSpeed Performance Report

Merging #10525 will not alter performance

_{Comparing dunder-all-ranges (a6fc510) with main (4f06d59)}

Summary

✅ 30 untouched benchmarks

[github-actions]

ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

✅ ecosystem check detected no linter changes.

Formatter (stable)

✅ ecosystem check detected no format changes.

Formatter (preview)

✅ ecosystem check detected no format changes.

[AlexWaygood]

I fixed the performance regressions initially reported by codspeed, and edited the PR description to reflect the new approach.