Update SwiftSyntax to version 510.0.0

[SimplyDanny]

No description provided.

[SwiftLintBot]

	2 Warnings
⚠️	If this is a user-facing change, please include a CHANGELOG entry to credit yourself! You can find it at CHANGELOG.md.
⚠️	This PR may need tests.

	17 Messages
📖	Linting Aerial with this PR took 1.27s vs 1.12s on main (13% slower)
📖	Linting Alamofire with this PR took 1.78s vs 1.61s on main (10% slower)
📖	Linting Brave with this PR took 10.35s vs 9.38s on main (10% slower)
📖	Linting DuckDuckGo with this PR took 5.39s vs 4.91s on main (9% slower)
📖	Linting Firefox with this PR took 13.85s vs 12.77s on main (8% slower)
📖	Linting Kickstarter with this PR took 12.24s vs 11.25s on main (8% slower)
📖	Linting Moya with this PR took 0.68s vs 0.62s on main (9% slower)
📖	Linting NetNewsWire with this PR took 3.41s vs 3.08s on main (10% slower)
📖	Linting Nimble with this PR took 1.02s vs 0.92s on main (10% slower)
📖	Linting PocketCasts with this PR took 9.86s vs 9.09s on main (8% slower)
📖	Linting Quick with this PR took 0.45s vs 0.41s on main (9% slower)
📖	Linting Realm with this PR took 6.36s vs 5.74s on main (10% slower)
📖	Linting Sourcery with this PR took 3.05s vs 2.79s on main (9% slower)
📖	Linting Swift with this PR took 6.15s vs 5.59s on main (10% slower)
📖	Linting VLC with this PR took 1.66s vs 1.52s on main (9% slower)
📖	Linting Wire with this PR took 23.31s vs 21.2s on main (9% slower)
📖	Linting WordPress with this PR took 15.18s vs 13.66s on main (11% slower)

Here's an example of your CHANGELOG entry:

* Update SwiftSyntax to version 510.0.0.  
  [SimplyDanny](https://github.com/SimplyDanny)
  [#issue_number](https://github.com/realm/SwiftLint/issues/issue_number)

note: There are two invisible spaces after the entry's text.

Generated by 🚫 Danger

[jpsim]

The 9-13% perf hit is unfortunate. Would be good to share those numbers with the SwiftSyntax folks.

[SimplyDanny]

While the improvements in memory management in apple/swift-syntax#2537 look very promising, the decision is against adding them to any Swift 510.x.y release. We might only see it in 600.0.0 earliest.

So what to do? Skip 510.x.y entirely and wait for 600.x.y or accept a performance drop of ~10%? @jpsim, what's your opinion?

[jpsim]

We should stay on the latest SwiftSyntax release because it’ll parse Swift 5.10 code more accurately. Higher accuracy is worth a 10% hit in perf in the uncached case.