Per Spec, allow Authorization Server to -maybe- issue a new Refresh Token.

 The authorization server MAY issue a new refresh token, in which case
   the client MUST discard the old refresh token and replace it with the
   new refresh token.  The authorization server MAY revoke the old
   refresh token after issuing a new refresh token to the client.  If a
   new refresh token is issued, the refresh token scope MUST be
   identical to that of the refresh token included by the client in the
   request.

This commit allows users to specifiy the time before the Refresh Token
expire time to issue a new Refresh Token.
Not sure what you mean here.

Granted, this is just a copy-paste extension from another test.  But I'm asserting that we are returning a refresh_token, regardless of my main change.  Then the different applies with the assertNotEquals, and assertEquals,, where we see the refresh_token coming out of the issueAccessToken()