Avoid creating stats keys with value "0"

The problem was that backend was reporting usages of 0 when they were included in requests to the authrep and report endpoints. Because of that, report jobs ended up creating stats keys with a value of 0. A stats key set to 0 is equivalent to a non-existing one when rate-limiting, so the feature was working correctly but wasting space in the DB.