fix: use API urls from official doc

[sevbch]

Context

API url to use isn't consistent with GitGuardian API documentation. Thus when users try to set API url param to https://api.gitguardian.com/v1 or https://api.eu1.gitguardian.com/v1, login fail.

What has been done

When a url from official documentation is provided, we replace it with its matching one working with GGShield.

Validation

• checkout this branch
• launch the extension
• set API url param to https://api.gitguardian.com/v1 or https://api.eu1.gitguardian.com/v1
• reload window
• you should have logged in perfectly

PR check list

• As much as possible, the changes include tests
• If the changes affect the end user (new feature, behavior change, bug fix) then the PR has a changelog entry.
  @salome-voltz @gg-jonathangriffe is there a way to add a changelog entry? Apart from updating CHANGELOG.md in the release PR?

[gg-jonathangriffe]

I think that the extension should prioritize being consistent with ggshield more than with the documentation.
In ggshield, settings the URL to https://api.gitguardian.com/v1 does not work, therefore I think we should keep it simple here and not do any additional treatment.
If we want to be more flexible, we should probably do it in ggshield.
WDYT ?

[sevbch]

I think that the extension should prioritize being consistent with ggshield more than with the documentation. In ggshield, settings the URL to https://api.gitguardian.com/v1 does not work, therefore I think we should keep it simple here and not do any additional treatment. If we want to be more flexible, we should probably do it in ggshield. WDYT ?

You're right, I implemented changes in GGShield in GitGuardian/ggshield#1045 . Let me know what you think.

Closing this PR