Using flask-login request_loader, we can validate jwt tokens.
This allows to use the same decorators for the web UI (using cookies)
and the API (using JWT) as well as the current_user local proxy.

https://black.readthedocs.io/en/stable/

To check if the unique object is the one being edited, we need to store
the object used to create the form in the form (_obj).
This is inspired from flask-admin.

Those tokens are supposed to be used in scripts or applications to
access the API and should not expire.

Updated to flask-jwt-extended 3.4.0 to be able to disable expiration
See https://github.com/vimalloc/flask-jwt-extended/issues/105

- All created tokens are stored in the database.
  To revoke a token, we just delete it from the database.
  Tokens not found in the database are thus considered unvalid / revoked.

- Add button to copy generated token to the clipboard

- Redesign profile page