fix(ios): move PrivacyInfo.xcprivacy to resource_bundles to fix build…

[mrgear111]

This PR fixes a build issue where PrivacyInfo.xcprivacy conflicts with other libraries (like when using Expo or React Native) because it was being copied to the main bundle root.

The Problem

When PrivacyInfo.xcprivacy is in s.resources, it gets copied to the top-level app bundle. If another library does the same thing, or if the build system (like Expo) tries to aggregate privacy manifests, it causes a "Multiple commands produce..." error.

The Fix

I've moved PrivacyInfo.xcprivacy to s.resource_bundles in both Capacitor.podspec and CapacitorCordova.podspec. This places the manifest inside its own bundle (e.g., Capacitor.bundle), which namespaces it correctly and allows Xcode/CocoaPods to handle the aggregation without conflicts.

This is the recommended approach for shipping privacy manifests in libraries.

Related Issue

Fixes #8259

Verification

• Verified that PrivacyInfo.xcprivacy is now defined under resource_bundles in the podspecs.
• This matches the standard fix for this class of errors.

Thanks!