Removing privacy sandbox property to resolve namespace conflict issue

Summary: The sandbox property causes [error](#1292) in advertisers app. Based on initial investigation, the issue is caused by Google and Meta both declare the same property in their own namespaces. This diff removes Meta's setting to provide a quick fix to the issue. Long term solutions need to be discussed with Google.

Reviewed By: maxalbrightmeta

Differential Revision: D68725513

fbshipit-source-id: 407a91feeaf1eeb7e8b7443e82ea0c5c169e19b6

facebook-core/src/main/AndroidManifest.xml

@@ -38,19 +38,7 @@
                 <action android:name="com.facebook.sdk.ACTION_CURRENT_AUTHENTICATION_TOKEN_CHANGED" />
             </intent-filter>
         </receiver>
-
-        <!-- Support for Google Privacy Sandbox adservices API -->
-        <property
-            android:name="android.adservices.AD_SERVICES_CONFIG"
-            android:resource="@xml/ad_services_config" />
-        <uses-library android:name="android.ext.adservices" android:required="false" />
     </application>
 
     <uses-permission android:name="com.google.android.gms.permission.AD_ID"/>
-
-    <!-- Support for Google Privacy Sandbox adservices API -->
-    <uses-permission android:name="android.permission.ACCESS_ADSERVICES_ATTRIBUTION" />
-    <uses-permission android:name="android.permission.ACCESS_ADSERVICES_AD_ID" />
-    <uses-permission android:name="android.permission.ACCESS_ADSERVICES_CUSTOM_AUDIENCE" />
-
 </manifest>