Update Swift Grammar and Queries

[levitatingpineapple]

This PR includes various improvements for swift language.

1. Adds swiftinterface to recognised file types as discussed in Support .swiftinterface files #10763
2. Updates tree-sitter-swift to 0.5.0. The corresponding highlight queries have been updated using 0.4.0...0.5.0 diff
3. Configures apple/swift-format as the formatter since it's the one used in the LSP code suggestions¹
4. Adds an inject query for the compile time regex literal. ²

5. Adds basic textobject queries for type, function, comment and argument.
   I tried to keep them similar to rust/textobjects.scm

demo.mp4

Footnotes

1. When formatter is invoked using a file path,
   it recursively looks for ".swift-formatter" configuration file in the parent directories.
   Since helix uses STDIN swift-format won't know where to look for the configuration.
   This is why --configuration .swift-format argument is used explicitly.
   To enable the formatter for a package: swift-format dump-configuration > $PACKAGE_ROOT/.swift-format ↩

2. Even though slash regex literals have been available since swift 5.7,
   they still need to be manually enabled for the target: swiftSettings: [.unsafeFlags(["-enable-bare-slash-regex"])] ↩

[WuerfelDev]

Regarding your comment at [1] about swift-format:

• a PR was merged into main (not yet in a release) where it searches for a .swift-format file in STDIN mode, using its cwd: Find configuration based on CWD when formatting from stdin swiftlang/swift-format#685
• I've created a PR there to search for a configuration file in config directories (eg ~/.config/swift-format/config.json) if nothing else was found: Search for configuration in config directories (dotfiles, etc) swiftlang/swift-format#749

Therefore a --configuration flag isn't needed once we get a new release (it would even block the other options from loading). FYI

[levitatingpineapple]

That's great to hear @WuerfelDev!
I am subscribed to https://github.com/apple/swift-format/releases.atom feed,
so I can remove the option once the new version is available. :)

Could you elaborate on:

it would even block the other options from loading

Do you mean the global config?

[WuerfelDev]

That's great to hear @WuerfelDev! I am subscribed to https://github.com/apple/swift-format/releases.atom feed, so I can remove the option once the new version is available. :)

Could you elaborate on:

it would even block the other options from loading

Do you mean the global config?

A invalid configuration file will return nil therefore not continuing to look for other configuration locations (neither cwd nor global).
It is a defined behavior as per this comment:
https://github.com/apple/swift-format/blob/4f19acc9acd4ff7bfe54ff58d32b5f1c3855a4a9/Sources/swift-format/Frontend/Frontend.swift#L190-L191

[tarikkirgin]

As a casual user I just wanted formatting to work on .swift files without having a .swift-format file. Felt quite unintuitive to have to delve into languages.toml to remove the --configuration flag as it is there by default.