docs(web-modeler): introduce gitlab sync

[marcellobarile]

Description

Introduces the GitLab sync functionality, which was added to the existing Git Sync feature.

Epic: https://github.com/camunda/product-hub/issues/2469
Part of https://github.com/camunda/web-modeler/issues/10911

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.

[github-actions]

👋 🤖 ✅ Looks like the changes were ported across versions, nice job! 🎉

You can read more about the versioning within our docs in our documentation guidelines.

[conceptualshark]

I've left a few suggestions here in two separate commits:

• A review of the content as-is here
• An option condensing the information into a tabbed display here

If you'd prefer not to introduce tabs at this time, I can roll back the second commit. You should be able to see the change in the deployed preview site, like this:

If any other repository hosts are planned, it will be helpful to have this scaffolding in place to add more options. Alternatively, we could look at creating a generic "Git Sync" page, and add options as their own independent subpages and reusable content. I'd be happy to take on some of this content structuring if it ends up being necessary, and it doesn't need to be decided or implemented here.

Otherwise this looks good to me! I'm approving for now, but can edit/adjust if the structure change isn't warranted at this time.

[marcellobarile]

@conceptualshark

An option condensing the information into a tabbed display

Yes! That's fantastic! We will indeed add more providers in the (near) future. Thanks!

[JacobiCamunda]

Looks good from my side, except one thing about the permissions.
But already approving 👍

[JacobiCamunda]

I added a new commit 0aaa103 to:

• address the new permissions we decided on
• rename "Project Access Token" to "Access Token" (See issue),
• Marked a GitHub limitation as GitHub specific
• Updated the info that a path will not be automatically created for GitLab if it does not already exist (This is contrary to GitHub, where this is possible)
• Added a note for self-hosted GitLab instances, similar to how it was done for GitHub (See here)

@conceptualshark, please give me another round of feedback or integrate your proposals directly.

CC: @wollefitz, you said we don't need to adjust the docs for the access token change but I changed it nonetheless to be transparent. I marked project access tokens as recommended but did not specify why. Maybe should just mark a personal access token as "not recommended" instead

[conceptualshark]

👍 This update looks good to me!

[christinaausley]

@marcellobarile Feel free to mark this as Ready for review and merge when you are ready 👍

[github-actions]

🧹 Preview environment for this PR has been torn down.