AndroidManifest: remove resources with maxSDK=22

Signed-off-by: Álvaro Brey Vilas <alvaro.brey@nextcloud.com>

src/main/AndroidManifest.xml

@@ -21,33 +21,11 @@
     xmlns:tools="http://schemas.android.com/tools"
     package="com.owncloud.android">
 
-    <!-- GET_ACCOUNTS is needed for API <= 22.
-        For API >= 23 results in the addition of CONTACTS group to the list of permissions that may be
-        dynamically disabled or enabled by the user after installation; but it is not important,
-        since GET_ACCOUNTS is an special case, the permission is not really needed to access accounts
-        owned by the app, our use case.
-        See note in http://developer.android.com/intl/es/reference/android/Manifest.permission.html#GET_ACCOUNTS -->
-    <uses-permission
-        android:name="android.permission.GET_ACCOUNTS"
-        android:maxSdkVersion="22" />
-
     <uses-permission android:name="android.permission.READ_CONTACTS" />
     <uses-permission android:name="android.permission.WRITE_CONTACTS" />
     <uses-permission android:name="android.permission.READ_CALENDAR" />
     <uses-permission android:name="android.permission.WRITE_CALENDAR" />
 
-    <!-- USE_CREDENTIALS, MANAGE_ACCOUNTS and AUTHENTICATE_ACCOUNTS are needed for API <= 22.
-        In API >= 23 they do not exist anymore -->
-    <uses-permission
-        android:name="android.permission.USE_CREDENTIALS"
-        android:maxSdkVersion="22" />
-    <uses-permission
-        android:name="android.permission.MANAGE_ACCOUNTS"
-        android:maxSdkVersion="22" />
-    <uses-permission
-        android:name="android.permission.AUTHENTICATE_ACCOUNTS"
-        android:maxSdkVersion="22" />
-
     <!-- WRITE_EXTERNAL_STORAGE may be enabled or disabled by the user after installation in
         API >= 23; the app needs to handle this -->
     <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />