This is the macOS analogue of #116493.

As of Xcode 16, App Store validation requires dSYM debug info bundles to be packaged inside application archives, as produced by the Product > Archive command in Xcode. For the moment, this is just a warning, but it seems entirely likely that this may become an error in some future release.

Steps required:

• In sky/tools/create_macos_framework.py, bundle FlutterMacOS.framework.dSYM inside Flutter.xcframework. In our case, the framework itself is located at FlutterMacOS.xcframework/macos-arm64_x86_64/FlutterMacOS.framework. The dSYM should be bundled at FlutterMacOS.xcframework/macos-arm64_x86_64/dSYMs/FlutterMacOS.framework.dSYM. macOS: Bundle dSYM packages in FlutterMacOS.xcframework engine#54696
• For backward compatibility, once the xcframework zip archive is produced, create and upload the current double-zipped FlutterMacOS.dsym.zip. macOS: Bundle dSYM packages in FlutterMacOS.xcframework engine#54696
• Patch the tool to ensure the dSYM is copied into the correct build directory location during flutter build macos. macOS: Copy macOS framework dSYM into build outputs #153975
• Update the entitlements test binariesWithoutEntitlements list. macOS: Add dSYM to binariesWithoutEntitlements #153977
• Manually test a macOS App Store upload.
• Delete the FlutterMacOS.dSYM.zip archives used for manual symbolication. macOS: Do not archive/upload FlutterMacOS.dSYM to cloud engine#54787