Don't drop below zero when calculating glory

Doesn't really matter anymore since this feature
is likely dead under the new Glory system but we
were showing negative glory values for players at
zero glory (season just reset).

This was definitely a bad bug for players using
the app without any comp history yet because even
when they weren't seeing negative values, they
were potentially still getting values lower than
what they would actually receive in-game. Which
sucks.

Profiles without any Glory is an obvious test
condition that I shouldn't have missed. Blargh.

Author: nathanhosselton

Fabled/Model/Profile.swift

@@ -170,7 +170,7 @@ public extension Profile {
 
         while matches < GloryRank.WeeklyMatchCompletionThreshold {
             matches += 1
-            points -= rank.lossDeficit
+            points = max(points - rank.lossDeficit, 0)
             rank = GloryRank(points: points)
         }
 

Fabled/ModelTests/ProfileTests.swift

@@ -469,6 +469,11 @@ class ProfileTests: XCTestCase {
         XCTAssert(profile.pessimisticGloryAtNextWeeklyReset == expectedAmount)
     }
 
+    func testPessimisticGloryAtNextWeeklyResetDoesNotReturnNegativeValues() {
+        let zeroGloryProfile = generateProfile(at: GloryRank(points: 0))
+        XCTAssertGreaterThanOrEqual(zeroGloryProfile.pessimisticGloryAtNextWeeklyReset, 0)
+    }
+
     func testOptimisticGloryAtNextWeeklyResetReturnsExpectedAmountWithNoMatchesYetPlayed() {
         let rank = GloryRank.heroic(.III)
         let profile = generateProfile(at: rank, progressOffset: 200) //ensures no profile rank-down with losses