Allow project access token to be used instead of personal token for GitLab integration

Who would benefit?

anyone using the integration with aha and GitLab

What impact would it make?

improves resiliency and stability of the integration

How should it work?

Currently, to set up the GitLab integration a user in GitLab must use a personal access token that is associated with their personal account. This means if this person leaves the company and the GitLab user is disabled, that the intetgration will fail.

To avoid this problem in other integrations, GitLab has a project access token that allows a similar identity validation/connection, but it is not associated with a single user, it is associated with a single project. This would allow the integration to be set up between aha workspace and gitlab project without having it tied to a specific user on the GitLab side.