Fix/direct outcomes

[emawby]

The primary goal of this PR is to fix Direct Sessions in the major release.

The problem was that we were relying on the foreground variable to decide if we should upgrade the session,

if (!foreground) {
        OneSignal.appEntryState = NOTIFICATION_CLICK;
        [OneSignal.sessionManager onDirectInfluenceFromNotificationOpen:_appEntryState withNotificationId:messageId];
}

and in the major release I had changed the setting of the foreground variable to:
let isAppForeground = [[UIApplication sharedApplication] applicationState] != UIApplicationStateBackground;
From:
let isAppForeground = [[UIApplication sharedApplication] applicationState] == UIApplicationStateActive;

This was to account for the inactive state which is technically in the foreground.

The first commit on this branch just flips it back to [[UIApplication sharedApplication] applicationState] == UIApplicationStateActive; to fix direct outcomes.

However, I don't think we need foreground or isActive to be passed around at all anymore. Since we are using the native iOS call for willShowInForeground we don't need to track the states on notification received. We were only logging those variables and (improperly) using them for direct outcomes. So I removed the foreground and isActive variables and am checking the state directly when deciding if we need to upgrade the session for direct outcomes.

I also added unit tests for outcomes while in the inactive state

This change is 

[Jeasmine]

Awesome! This is way more clear

[jkasten2]

Test failing, this is ok but @emawby please confirm tests pass locally?
We can fix the log limit in another PR as it is unrelated to this one.

[emawby]

The unit tests pass locally

[jkasten2]

@emawby 👍 Merge it in!