GitLab API results are not cached, causes high CPU usage on GitLab server

I've run into an issue where my private GitLab instance is flooded by requests from verdaccio GitLab, forcing 6 cores to all run at 100% capacity due to the `puma` workers in GitLab.

The promises for the GitLab API calls for `GitlabAPI.users.current()`, `GitlabAPI.Groups.all`, and `GitlabAPI.Projects.all` could be cached to avoid spamming the GitLab API with multiple similar requests