chore(ios) handle Apple privacy manifest changes

[hansemannn]

Todos

• Identify affected APIs
• Guard affected APIs by pre-compile statements if used in single methods / properties
• Document privacy changes for the affected APIs
• Add a guide for the new privacy changes (Done, here]
• Generate privacy manifest for APIs that have to be declared by default (e.g. Ti.App.Properties and Ti.App.iOS.UserDefaults) as well as own APIs (e.g. modules)
• Submit several test builds to verify the fixes

Context

There are more and more warnings popping up around privacy changes at Apple recently, generating some warning when uploading a build to App Store Connect:

ITMS-91053: Missing API declaration - Your app’s code in the “MyApp” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryDiskSpace. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app’s privacy manifest to provide approved reasons for these APIs used by your app’s code. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api.

ITMS-91053: Missing API declaration - Your app’s code in the “MyApp” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDefaults. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app’s privacy manifest to provide approved reasons for these APIs used by your app’s code. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api.

ITMS-91053: Missing API declaration - Your app’s code in the “MyApp” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryFileTimestamp. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app’s privacy manifest to provide approved reasons for these APIs used by your app’s code. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api.

ITMS-91053: Missing API declaration - Your app’s code in the “MyApp” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategorySystemBootTime. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app’s privacy manifest to provide approved reasons for these APIs used by your app’s code. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api.

Most of them are used in Ti.Filesystem APIs, so I will try to add guard for them or replace them with more top-level APIs. The docs will also be changed to make sure developers know about the priacy keys when using certain file APIs.

This will take some more time, but a PR should be ready by next week! Apple does not block apps with these warnings, yet, but it'll be good to be up-to-date as one of the first app frameworks (again) :leichtes_lächeln:

In addition, I'll try to support the "privacy manifest" in Titanium, a special configuration file that needs to be embedded into the generated Xcode project. Fun fun fun!

Code strong! 🚀

[cb1kenobi]

This is awesome! Great work!

[hansemannn]

Okay, our test builds all gone through while triggering warnings before. I think this is ready to merge!