Add missed key into privacy manifest

[mojganii]

Apple notified us that we missed NSPrivacyAccessedAPICategoryFileTimestamp in our privacy manifest. This pull request introduces this functionality.

---

This change is 

[linear]

IOS-595 Backport changes to the manifest from the release branch

[buggmagnet]

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @mojganii)

---

ios/MullvadVPN/Supporting Files/PrivacyInfo.xcprivacy line 16 at r1 (raw file):

                <key>NSPrivacyAccessedAPITypeReasons</key>
                <array>
                    <string>C617.1</string>

Please also add reason 3B52.1 because we are also using DocumentPickerViewController now in IP Overrides and we forgot to add it back then.

[rablador]

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @buggmagnet)

---

ios/MullvadVPN/Supporting Files/PrivacyInfo.xcprivacy line 16 at r1 (raw file):

Previously, buggmagnet wrote…

Please also add reason 3B52.1 because we are also using DocumentPickerViewController now in IP Overrides and we forgot to add it back then.

3B52.1 isn't related to DocumentPickerViewController though, right? That one only concerns reading file timestamps and such, which we don't read in ip overrides.

[mojganii]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @buggmagnet)

---

ios/MullvadVPN/Supporting Files/PrivacyInfo.xcprivacy line 16 at r1 (raw file):

Previously, rablador (Jon Petersson) wrote…

3B52.1 isn't related to DocumentPickerViewController though, right? That one only concerns reading file timestamps and such, which we don't read in ip overrides.

based on the apple's document(https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api), is it required when we are gonna have access to meta data of a file.do we need to have access meta data of a file?

btw it wouldn't hurt to have that, I don't know if it's required for our upcoming log file operations or not.

[mojganii]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @buggmagnet)

---

ios/MullvadVPN/Supporting Files/PrivacyInfo.xcprivacy line 16 at r1 (raw file):

Previously, mojganii wrote…

based on the apple's document(https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api), is it required when we are gonna have access to meta data of a file.do we need to have access meta data of a file?

btw it wouldn't hurt to have that, I don't know if it's required for our upcoming log file operations or not.

I'll add it.

[buggmagnet]

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @mojganii and @rablador)

---

ios/MullvadVPN/Supporting Files/PrivacyInfo.xcprivacy line 16 at r1 (raw file):
From the docs

Declare this reason to access the [...] directories that the user specifically granted access to, such as using a document picker view controller.

It's not explained in the best terms, but I think that boils down to "If you use DocumentPickerViewController, you have to use this reason.
Because we cannot have more granularity than either full access to documents, or no access to documents AFAICT

[mojganii]

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @buggmagnet and @rablador)

---

ios/MullvadVPN/Supporting Files/PrivacyInfo.xcprivacy line 16 at r1 (raw file):

Previously, buggmagnet wrote…

From the docs

Declare this reason to access the [...] directories that the user specifically granted access to, such as using a document picker view controller.

It's not explained in the best terms, but I think that boils down to "If you use DocumentPickerViewController, you have to use this reason.
Because we cannot have more granularity than either full access to documents, or no access to documents AFAICT

Done.

[rablador]

Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @buggmagnet)

[buggmagnet]

Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved

[rablador]

Reviewable status: complete! all files reviewed, all discussions resolved

[pinkisemils]

Reviewed all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved

[github-actions]

🚨 End to end tests failed. Please check the failed workflow run.