Fails to recongise GitLab project in repository without `origin` remote

Summary

The extension fails to associate current workspace with GitLab project if the project doesn't have default remote (e.g. origin).

Found during testing the 3.0.0 release #146 (closed).

Steps to reproduce

1. remove all remotes
   • git remote -v
   • git remove <remote name> for each remote.
2. add two not custom origins
   • git remote add test <gitlab repo url>
   • git remote add test2 <gitlab repo url>

What is the current bug behavior?

The extension doesn't recognize that that the workspace is a GitLab project.

What is the expected correct behavior?

Extension should the project associated with test remote.

Possible fixes

The critical part is that we get git remote command result and we are not handling scenario when there is multiple remotes.

https://gitlab.com/gitlab-org/gitlab-vscode-extension/-/blob/66cf4ee08e7ed183dd18b8c8cd0fb54044397fce/src/git_service.js#L116