Native assets support for MacOS and iOS

[dcharkes]

Support for FFI calls with @Native external functions through Native assets on MacOS and iOS. This enables bundling native code without any build-system boilerplate code.

For more info see:

• ☂️ Native assets support #129757

Implementation details for MacOS and iOS.

Dylibs are bundled by (1) making them fat binaries if multiple architectures are targeted, (2) code signing these, and (3) copying them to the frameworks folder. These steps are done manual rather than via CocoaPods. CocoaPods would have done the same steps, but (a) needs the dylibs to be there before the xcodebuild invocation (we could trick it, by having a minimal dylib in the place and replace it during the build process, that works), and (b) can't deal with having no dylibs to be bundled (we'd have to bundle a dummy dylib or include some dummy C code in the build file).

The dylibs are build as a new target inside flutter assemble, as that is the moment we know what build-mode and architecture to target.

The mapping from asset id to dylib-path is passed in to every kernel compilation path. The interesting case is hot-restart where the initial kernel file is compiled by the "inner" flutter assemble, while after hot restart the "outer" flutter run compiled kernel file is pushed to the device. Both kernel files need to contain the mapping. The "inner" flutter assemble gets its mapping from the NativeAssets target which builds the native assets. The "outer" flutter run get its mapping from a dry-run invocation. Since this hot restart can be used for multiple target devices (flutter run -d all) it contains the mapping for all known targets.

Example vs template

The PR includes a new template that uses the new native assets in a package and has an app importing that. Separate discussion in: #131209.

Tests

This PR adds new tests to cover the various use cases.

• dev/devicelab/bin/tasks/native_assets_ios.dart
  • Runs an example app with native assets in all build modes, doing hot reload and hot restart in debug mode.
• dev/devicelab/bin/tasks/native_assets_ios_simulator.dart
  • Runs an example app with native assets, doing hot reload and hot restart.
• packages/flutter_tools/test/integration.shard/native_assets_test.dart
  • Runs (incl hot reload/hot restart), builds, builds frameworks for iOS, MacOS and flutter-tester.
• packages/flutter_tools/test/general.shard/build_system/targets/native_assets_test.dart
  • Unit tests the new Target in the backend.
• packages/flutter_tools/test/general.shard/ios/native_assets_test.dart
• packages/flutter_tools/test/general.shard/macos/native_assets_test.dart
  • Unit tests the native assets being packaged on a iOS/MacOS build.

It also extends various existing tests:

• dev/devicelab/bin/tasks/module_test_ios.dart
  • Exercises the add2app scenario.
• packages/flutter_tools/test/general.shard/features_test.dart
  • Unit test the new feature flag.

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
• I signed the CLA.
• I listed at least one issue that this PR fixes in the description above.
• I updated/added relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or this PR is test-exempt.
• All existing and new tests are passing.