Support for custom authentication provider

[PierreSchwang]

Implement support as described in #240

[vercel]

@PierreSchwang is attempting to deploy a commit to a Personal Account owned by @electerious on Vercel.

@electerious first needs to authorize it.

[PierreSchwang]

I'm unsure right now, theoretically it would work, but since the /api endpoint for ackee-tracker has to be public, doesn't that also mean that the GraphQL query to retrieve stats is now public as well? I don't know how to solve this at all....

[electerious]

@PierreSchwang How are you protecting the UI of Ackee? Isn't it possible to protect the API in the same way?

[PierreSchwang]

Yeah, but does the api not get used by the ackee script?

[electerious]

That's true. Not sure if there's a way to get around this problem. It's a GraphQL API so the endpoint for both ackee-tracker and Ackee is the same. This makes it impossible to allow ackee-tracker requests only.

[PierreSchwang]

Yeah, thats what i thought. I may take a further look into that

[electerious]

I will close the PR as there's currently no solution to solve the authentication problem.