Move API key name to first column

[bafonins]

Summary

References #875

then maybe we should make the columns ID, name, rights.

[htdvisser]

This may be a bit confusing. API key lists are currently sorted by their ID, so if the console now starts presenting this name as the first field, users will be confused if the list isn't sorted by that field, right?

[johanstokking]

Yeah good point. If we keep the sorting by ID (makes sense, name is optional), then maybe we should make the columns ID, name, rights.

[bafonins]

then maybe we should make the columns ID, name, rights.

How is this better than the order before?

[johanstokking]

then maybe we should make the columns ID, name, rights.

How is this better than the order before?

The name was burried on the right

[bafonins]

updated description

[coveralls]

Coverage decreased (-0.02%) to 73.071% when pulling 81c817a on feature/change-api-keys-table-headers into ac50229 on master.

[kschiffer]

The ID value is very unhelpful IMO. I don't see any user scanning the table by a cryptic hash value. If we can, we should really sort by creation date or the name value. We might even consider making the name field mandatory, or setting default values like API Key 1, which I would recommend. We can then hide or at least abbreviate the ID field in the table view (that is, if there is no essential use of the ID value that I have missed).

[kschiffer]

Approving with regards to: #875 (comment)