Implement names for API keys.

[ro-tex]

PULL REQUEST

Overview

Example for Visual Changes

Checklist

Review and complete the checklist to ensure that the PR is complete before assigned to an approver.

• All new methods or updated methods have clear docstrings
• Testing added or updated for new methods
• Verify if any changes impact the WebPortal Health Checks
• Approriate documentation updated
• Changelog file created

Issues Closed

Closes #155

[peterjan]

shouldn't API key names be unique per user?

[ro-tex]

shouldn't API key names be unique per user?

I see no reason to introduce such a limitation. That will mean that there can be only one API key without a name (the name is ""). Even if we add an exception for that, people might want to name their API keys according to the machine that's using them or something like this.

Overall, I don't see an unequivocal benefit of adding this limitation.