1969 enhancement frontend component jwtapikey

[correct-horse-battery-bench]

DRAFT

Can only be merged when https://github.com/hashtopolis/server/pull/2067/changes has been accepted.

[correct-horse-battery-bench]

Open questions:

1. It would probably be nice to view the permissions for an existing api key, but the permissions are only baked into the jwt token and there is no option to get them as the token is also not saved on the backend. Maybe store the permissions as json in the db as well -> requires backend change
2. It would probably be nice if we could name the jwt tokens
3. What about migrations what happens with existing jwt token