Xcode 13.3 broke analyzer rules

[jpsim]

New Issue Checklist

• Updated SwiftLint to the latest version
• I searched for existing GitHub issues

Describe the bug

I think Xcode 13.3 broke something in how we run analyzer rules.

Seeing a lot of "Could not get cursor info" errors here: https://buildkite.com/swiftlint/swiftlint/builds/2484#2158175e-0903-44bf-ae35-83500f324d1d

Steps to repro: DEVELOPER_DIR=/Applications/Xcode-13.3.app/Contents/Developer make analyze

Complete output when running SwiftLint, including the stack trace and command used

N/A

Environment

• SwiftLint version (run swiftlint version to be sure)? master and 0.47.0 are affected
• Installation method used (Homebrew, CocoaPods, building from source, etc)? All
• Paste your configuration file: https://github.com/realm/SwiftLint/blob/master/.swiftlint.yml
• Are you using nested configurations? No.
• Which Xcode version are you using (check xcodebuild -version)? Xcode 13.3 (13E113)
• Do you have a sample that shows the issue? DEVELOPER_DIR=/Applications/Xcode-13.3.app/Contents/Developer make analyze

[jpsim]

Oof. It all works if I disable all concurrency in SwiftLint. I looks like SourceKit as of Xcode 13.3 is now canceling in-flight requests when a new request comes in. I'll dig to see if there's a way to turn that off.

[jpsim]

Another way I can work around the issue is by setting "key.cancel_on_subsequent_request": 0 https://github.com/apple/swift/blob/931449bc0e038c594c12dd126edd7ec74f4cf907/utils/gyb_sourcekit_support/UIDs.py#L144 but now I'm investigating a significant performance regression in SourceKit going from Xcode 13.2.1 to 13.3.

[jpsim]

Fixed in #3921 but still has significant performance regressions.