In fosite, why is the new RotateRefreshToken interface function also responsible for revoking the old access token?

[cfryanr]

Starting in fosite v0.49.0, during a refresh grant for a token endpoint, the new RotateRefreshToken storage interface function must also revoke the access token to maintain correct behavior. Why does a function called RotateRefreshToken have anything to do with revoking an old access token, where there is already another storage interface for revoking an access token? In other words, why doesn't PopulateTokenEndpointResponse in flow_refresh.go call RevokeAccessToken anymore? Is this conflating refresh and access token storage interfaces?

[cfryanr]

@aeneasr I think this change came from one of your PRs? Perhaps you can shed some light for the users of fosite? Thanks!