Release 0.1.1

Breaking Changes

Authorization Server now points to URI starting /auth/*
If you find your workflow failing due to this change, you may be facing one of the following issues:
- Distinct Authorization and Resource Servers. The new API design splits the API into Authorization and Resource servers and treats their paths differently. All the authentication requests are now re-routed to paths with the prefix /auth/.
Custom Exception Handlers. All the intended exceptions are now raised from custom exceptions catering to the exact scenario. Intended Exceptions are no longer raised as generic python exceptions. Custom exceptions now give coherent descriptions to identify the root cause of the error.

/auth/use_refresh_token
- New route to implement rotational access tokens for a smooth user experience and enhancing security.
- A new set of tokens is issued at the time of expiry of the previous access tokens.
CORS Middleware
- Middleware to allow CORS data exchange.

Wrong decode key pass
- Refresh access tokens were being decoded by the wrong API key resulting in unexpected authentication failures after the access token's expiry.
- Refresh token's API key is now fixed.
village_name parameter was not being considered a part of the authentication process.
- The fix includes this parameter as a part of the authentication process and will be hashed before dumping to the database.