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

main blueprint splitted in:
- inventory
- networks

- 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