chore: Read Gitlab server URL from env for prime integrations

[Dschoordsch]

Description

Right now it is hardcoded, but private Gitlab instances behave like the public one, so for some Parabol instances it might make sense to point it to a different Gitlab instance.

Demo

https://www.loom.com/share/bd9d06ef81b74f74b46ca2e80af04383?sid=3e3369ab-3e94-4d7e-8fb2-7d960cffe032 🔒

Testing scenarios

• Set the URL
• run yarn build && yarn predeploy
• check the correct value is set in PG

Final checklist

• I checked the code review guidelines
• I have added Metrics Representative as reviewer(s) if my PR invovles metrics/data/analytics related changes
• I have performed a self-review of my code, the same way I'd do it for any other team member
• I have tested all cases I listed in the testing scenarios and I haven't found any issues or regressions
• Whenever I took a non-obvious choice I added a comment explaining why I did it this way
• I added the label Skip Maintainer Review Indicating the PR only requires reviewer review and can be merged right after it's approved if the PR introduces only minor changes, does not contain any architectural changes or does not introduce any new patterns and I think one review is sufficient'
• PR title is human readable and could be used in changelog

[rafaelromcar-parabol]

Other than my inline comment, LGTM.

This would be a great use case for you to test the process of adding a new environment variable to the application 😸 You have Loom videos and documentation explaining how to do it, but please, let me know if you need any help with that 😃

[rafaelromcar-parabol]

Why a default value? IMHO we should just use the env GITLAB_SERVER_URL and on the .env.example we can have our default value.

[Dschoordsch]

I did not want to touch the current deployments without any need.

[rafaelromcar-parabol]

It's true that removing that default value is a breaking change. Ok, let's keep it there.

I'm just against default hardcoded values in general 😸