Including QStandardPaths on iOS forces us to include unnecessary capabilities

(Apologies, I'm sure I've picked the wrong component.)

I use `QStandardPaths::AppDataLocation` and `QStandardPaths::TempLocation` in my app and no other parts of `QStandardPaths`.

Back in Qt 5, I discovered that simply including `QStandardPaths` caused an App Store rejection, requiring me to add a bogus NSPhotoLibraryUsageDescription capability to my Info.plist.

In Qt 6.4.2, I have just had another App Store rejection, this time requiring me to add a bogus NSCameraUsageDescription capability too.

(Perhaps if I do this I will get further rejections; I don't know yet.)

Adding capabilities that aren't used and cannot be justified to Apple risks further rejections. And doesn't make for good practice in any case.

Please can QStandardPaths be 'fixed' so that the sensitive parts of the library do not get included unless they are being specifically used.

As a poor fallback, please could the documentation give developers for iOS a full list of all capabilities they will need to include if using the library.