Add privacy manifest file

[danielepantaleone]

This PR adds an empty Privacy Manifest file. Although a Privacy Manifest may be not needed for GRDB since no privacy sensitive API is used within the library, as mentioned already in #1480, adding an empty one doesn't compromise library functionalities in any way.

This solves #1479 and #1489.

Pull Request Checklist

• CONTRIBUTING: You have read https://github.com/groue/GRDB.swift/blob/master/CONTRIBUTING.md
• BRANCH: This pull request is submitted against the development branch.
• DOCUMENTATION: Inline documentation has been updated.
• DOCUMENTATION: README.md or another dedicated guide has been updated.
• TESTS: Changes are tested.
• TESTS: The make smokeTest terminal command runs without failure.

[groue]

Hello @danielepantaleone. It's nice to see you again, and thank your for presenting this welcome contribution for what it is.

Would you please add the manifest to GRDBCustom.xcodeproj as well, as mentioned in the checklist?

I'll check the PR after that.

[danielepantaleone]

Sure, I'll add it as soon as I can 😊

[groue]

Thanks @danielepantaleone, I'll review shortly.

[groue]

OK @danielepantaleone. I amended your pull request:

• CocoaPods integration was not tested, and does not work: bbe7d2f
• The resource was not added to any target in GRDB.xcodeproj: bb44f48

I'm waiting for the CI to complete, and I should be able to merge next after.

[groue]

Thank you @danielepantaleone, the privacy manifest has shipped in v6.25.0 👍

[danielepantaleone]

Thanks! I didn't know that Cocoapods doesn't support the Privacy manifest. I did some research on StackOverflow to understand how to add resource files to a podspec, which is the reason why I added the file in the "resources" variable of the podspec.

Thanks again for shipping the new version though 😃

[groue]

Yes, I understand. I have a workspace that integrates GRDB with CocoaPods and I could inspect the application bundle and see that our privacy manifest was copied at the root of the bundle, which is not correct. Anyway, the landscape has changed since you have opened #1479 and I mentioned that CocoaPods support was desired: I can no longer publish a new version on CocoaPods anyway 😅 (CocoaPods/CocoaPods#11839).

I hope this new version will remove any problem with GRDB at your workplace.