Implement offline tokens natively in Auth

[sbose78]

as a dependency of #350

What are offline tokens?
https://fabric8-services.github.io/fabric8-auth/reference.html#_offline_tokens

Token issuance:

If /api/login has scope=offline_access param,
generate a token with an expiry of 365 days.

Token validation and usage

1. Validate if the token is an offline token using the "jti" claim, and if yes, check if it was last used within 30 days using the TOKEN_ACCESS_LOG table ( https://www.dbdesigner.net/designer/schema/98194 )
2. If yes, generate a new access token and return it.

Dependencies:

• TOKEN table Add a table for storing issued token info #582

[sbose78]

( move to different place.. )

1. Store access/refresh/offline token info in TOKEN table ( to be renamed from RPT token table )
   https://www.dbdesigner.net/designer/schema/98194 . This endpoint Add 'invalidate all tokens' for a user API endpoint #580 can be used invalidate all tokens a user is currently using.

2. Add a new token access log table.

3. Use the info in (2) for offline token usage: An offline token is a special refresh token which if not used more than once in 30 days expires.

[xcoulon]

Offline tokens will not be supported in the future, so no need to implement this feature in fabric8-auth