rm push registration string 3000 error parsing

* It is not reliable to use a string check on an error message to map
to a specific OneSignal error code.
* Second there is only one reason you would get a 3000 error code,
the push notification capability is not enabled.
  - The 3000 "other" error that was being reported was never a thing.
  - This "other" 3000 error happens when the device is not set to
  English.
  - Also recently (iOS 13 or 14) the English error message changed.
* This means we will no longer see the confusing "Other Apns 3000 Error"
  message on the OneSignal dashboard and will now see the correct
  "Missing Push Capability".

Author: jkasten2

iOS_SDK/OneSignalSDK/Source/OneSignal.m

@@ -1603,15 +1603,9 @@ + (void)handleDidFailRegisterForRemoteNotification:(NSError*)err {
     waitingForApnsResponse = false;
 
     if (err.code == 3000) {
-        if ([((NSString*)[err.userInfo objectForKey:NSLocalizedDescriptionKey]) rangeOfString:@"no valid 'aps-environment'"].location != NSNotFound) {
-            // User did not enable push notification capability
-            [OneSignal setSubscriptionErrorStatus:ERROR_PUSH_CAPABLILITY_DISABLED];
-            [OneSignal onesignal_Log:ONE_S_LL_ERROR message:@"ERROR! 'Push Notification' capability not turned on! Enable it in Xcode under 'Project Target' -> Capability."];
-        }
-        else {
-            [OneSignal setSubscriptionErrorStatus:ERROR_PUSH_OTHER_3000_ERROR];
-            [OneSignal onesignal_Log:ONE_S_LL_ERROR message:[NSString stringWithFormat:@"ERROR! Unknown 3000 error returned from APNs when getting a push token: %@", err]];
-        }
+        // User did not enable push notification capability
+        [OneSignal setSubscriptionErrorStatus:ERROR_PUSH_CAPABLILITY_DISABLED];
+        [OneSignal onesignal_Log:ONE_S_LL_ERROR message:@"ERROR! 'Push Notification' capability not turned on! Enable it in Xcode under 'Project Target' -> Capability."];
     }
     else if (err.code == 3010) {
         [OneSignal setSubscriptionErrorStatus:ERROR_PUSH_SIMULATOR_NOT_SUPPORTED];