director: Fix off-by-one when checking if user weakness is stuck

When the weakness was exactly at the second, the weakness wasn't detected
and the next expiration timeout was removed entirely. This shouldn't have
caused any bigger problems, because another user lookup on the following
second would have then detected the weakness, removed the user and restored
the next expiration timeout.

src/director/user-directory.c

@@ -82,7 +82,7 @@ static bool user_directory_user_has_connections(struct user_directory *dir,
 	}
 
 	if (user->weak) {
-		if (expire_timestamp + USER_NEAR_EXPIRING_MAX >= ioloop_time) {
+		if (expire_timestamp + USER_NEAR_EXPIRING_MAX > ioloop_time) {
 			*retry_secs_r = expire_timestamp +
 				USER_NEAR_EXPIRING_MAX - ioloop_time;
 			return TRUE;