Adding authorisation options for API access

[bpiraeus]

Fixes #

Requirements

All new code should be covered with tests, documentation should be updated. CI should pass.

Description of the Change

Checklist

• unit-test added (if change is algorithm)
• functional test added/updated (if change is functional)
• man page updated (if applicable)
• bash completion updated (if applicable)
• documentation updated
• author name in AUTHORS

[bpiraeus]

I went through the failing tests, and unless I'm missing something, those are not from my changes, not sure what I can do about that short of refactoring someone else's code. I'm happy to muck around if needed, but you'd likely prefer someone with a lot more chops than myself to mitigate those issues.

[randombenj]

@bpiraeus It looks like mostly deprecation errors

• x/crypto/openpgp: mark as frozen and deprecated golang/go#44226
• package golang.org/x/crypto/ssh/terminal is deprecated: this package moved to golang.org/x/term

If you want to, feel free to investigate if there are some simple fixes for the deprecated packages (x/term) seems to be quite an easy one, not sure about the crypto one ...

[bpiraeus]

Cleaned up a few oddballs in my code that gosimple flagged, also moved the terminal bits to the appropriate package, the pgp ones appear as if they're likely going to want 3rd party library.

[neolynx]

introducing authorization per repo is a nice idea.

however, authentication without SSL is not that nice, so probably we should implement this as well with this change.

since different authentication types are supported, the variable LdapGroup should probably AuthorizedGroup

[neolynx]

rebased on master