Merge request support for gitlab

[johannes-graeter]

Problem Statement

Although merge/pull requests are supported for the github connections, for gitlab only issues are supported.
It would be great to also support merge requests just as in the github connection.

❔ Possible Solution

From trying around with the gitlab api, I understand that the scope issues or merge-requests always has to be specified.
I would suggest to use add an option "expert mode" in the connection settings and if that is set parse everything from the input box to the api, so in line

super-productivity/src/app/features/issue/providers/gitlab/gitlab-api/gitlab-api.service.ts

Line 122 in d0f2fa1

url: `${this._apiLink(cfg)}/issues?search=${searchText}${this.getScopeParam(

not prefill the api query but leave that to the user.
A doc that would suggest to use the gitlab filters on gitlab.com and copy the search url might be helpful to guide people on how to compose the search.

⤴️ Describe alternatives you've considered

• Adding a merge request checkbox, that would replace "issue" scope with "merge_requests", however the search options in the api vary a lot, so that does not make sense
• having a single gitlab api query for both issues and merge_requests (similar to github) but this does not seem to exist

➕ Additional context

The new gitlab merge request skin is extremely confusing, so I searched for a tool to manage those better.
Since I wanted to up my todo lists anyways I loved your project from the beginning. However in my company we are using both github and gitlab. Also we manage tickets not in gitlab, so merge requests are the only thing I have here. while it works nicely for github, I can not manage gitlab merge requests which is a pity.

If you agree on the solution @johannesjo I am also willing to do the impl (even though my ts is ... quite basic)

[github-actions]

Thank you very much for opening up this issue! I am currently a bit overwhelmed by the many requests that arrive each week, so please forgive me, if I fail to respond personally. I am still very likely to at least skim read your request and I'll probably try to fix all (real) bugs if possible and I will likely review every single PR being made (please, give me a heads up if you intent to do so) and I will try to work on popular requests (please upvote via thumbs up on the original issue) whenever possible, but trying to respond to every single issue over the last years has been kind of draining and I need to adjust my approach for this project to remain fun for me and to make any progress with actually coding new stuff. Thanks for your understanding!

[github-actions]

Hello there johannes-graeter! 👋

Thank you and congratulations 🎉 for opening your very first issue in this project! 💖

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀

For more open ended discussions and/or specific questions, please visit the discussions page. 💖