decodeActivityType incorrect string comparison causes AutomotiveNavigation

[atorger]

The MAURConfig.m function decodeActivityType has incorrect string comparisons. Now it checks if the value is nonzero, which means the strings are NOT the same, rather than the other way around as it should be. This means that activity type typically ends up at AutomotiveNavigation regardless what you set which leads to map matching / road snapping which you may not want to have. In case I had set the Fitness activity type but strangely got road snapping, that's how I debugged and eventually found the problem. With correct activity applied, road snapping disappeared.

The string comparisons should be changed to if ([....] == NSOrderedSame) { ... } then it will work.