Description

Update Xcode compatibility version for iOS app and module templates from 3.2 to 9.2 (the default for new Xcode projects).

This prevents Xcode from dropping into a "legacy build location" state that is incompatible with Swift Package Manager.

Also, generate workspace check files so the user doesn't have new unexpected files to stage and commit after running in Xcode.

I don't think this warrants a migration since most users are not going to be importing Swift packages. The manual migration is to go into the File inspector and swap Project Format from "Xcode 3.2-compatible" to "Xcode 9.3-compatible".

or to solve the Swift package manager sisue directly, swap File > Project Settings > Per-User Project Settings: > Advanced from Legacy to Xcode Default

Related Issues

Fixes #44811.

Tests

Updated create tests.

Checklist

• I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
• I signed the [CLA].
• I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
• I read the [Tree Hygiene] wiki page, which explains my responsibilities.
• I updated/added relevant documentation (doc comments with ///).
• All existing and new tests are passing.
• The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

• No, no existing tests failed, so this is not a breaking change.
• Yes, this is a breaking change. If not, delete the remainder of this section.