Aiohttp-jwt

* Fixed issue with non bearer token scheme [14](https://github.com/hzlmn/aiohttp-jwt/issues/14). Thanks [vikitikitavi](github.com/vikitikitavi)

* Added [support](https://github.com/hzlmn/aiohttp-jwt/commit/59fce065af9f29c32a7ba8e07e963cc294c2734c) for checking revoked tokens

Now users can pass `is_revoked` callback that should return bool value that indicates token status and in case of True, middleware will raise HTTPForbidden with `Token is revoked` message.

* Better description for token decoding error.

* Added more usage [examples](https://github.com/hzlmn/aiohttp-jwt/pull/12). Thanks [vikitikitavi](github.com/vikitikitavi)

* Refactored handling of broken provided token.

* Revisited naming of certain properties and helpers.

- `ONE_OF` to `match_any`
- `ALL_IN` to `match_all`
- `strategy` to `comparison`


* Improved overall code test coverage.

* Introduced [check_permissions](https://github.com/hzlmn/aiohttp-jwt/blob/master/aiohttp_jwt/decorators.pyL22-L48) decorator for providing [scope based](https://tools.ietf.org/html/rfc6749section-3.3) permission model for your application handlers.

Permissions should be described as an array of strings inside the JWT token, or as a space-delimited OAuth 2.0 Access Token Scope string.

* Introduced [JWT](https://jwt.io/) middleware for encoding/verifying your JWT token and setting property on [aiohttp.Request](https://docs.aiohttp.org/en/stable/web_reference.htmlrequest-and-base-request) object.