Using Dawn triggers a privacy-manifest problem with apple appstoreconnect submissions

[SoylentGraham]

Dawn uses abseil, which appears on apple's "privacy api using" list.
Dawn only uses string functions (Lost url to this citation), and abseil itself apparently is safe abseil/abseil-cpp#1604

To remedy this, the target that uses abseil (the emails from apple cite libwebgpu_dawn.dylib) we can add a PrivacyInfo.xcprivacy resource to our target (I'm using DawnNative as that's where I have my xcframework)

This generates a .bundle in my final .app output containing the privacy manfiest, which hopefully allows submission

[SoylentGraham]

Note; adding to the DawnNative target, means app now also need to include the DawnNative.lib generated by swift.
Maybe we can move the privacy to WebGpu target... have to see what apple approve

[SoylentGraham]

The above change hasn't worked - I think I need to turn that dylib into a framework and include it there
https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/adding_a_privacy_manifest_to_your_app_or_third-party_sdk
Or possibly I can manually make a .bundle (as spm generates) and perhaps that will make it into the .xcframework
swift-webgpu_DawnNative.bundle.zip