Automation of crowdin project creation and management

[NotMyFault]

What feature do you want to see added?

This is a continuation of the helpdesk issue: https://github.com/jenkins-infra/helpdesk/issues/2918#issuecomment-1123890859

The original idea of @lemeurherve to provide a more streamlined and automated solution, instead of raising helpdesk issues for the project creation of crowdin projects. I'm a bit short on time at the moment, hence I can't work on such an implementation through the RPU, but I'll leave some resources and the workflow Mark and me are using, to manage these infra tickets by hand, in case someone else is interested in it.

Workflow

Prerequisites:

• The user(s) to add have logged in crowdin.jenkins.io initially

  Project creation:

• A new project and team on crowdin.jenkins.io are created, using the same name like the Jenkins plugin on GitHub.
• The created team is added to the project and granted manager permissions.
• The members listed on the help desk issue are added to the team.

Implementation

To keep it simple, a new sequence could be added to the files in the permissions directory, a plugin maintainer opts in, if they want to use crowdin.jenkins.io:

...
crowdin_managers:
  - userOne
  - userTwo
  - ...

Members listed are managers of that plugin on our Crowdin instance.

Resources

Crowdin provides an extensive API and Java library the RPU can utilize.

Upstream changes

No response

[lemeurherve]

@NotMyFault @MarkEWaite WDYT of adding a checkbox in the hosting request template to ask if the plugin has to be integrated with Crowdin? A "crowdin" label could then be automatically added if the checkbox is ticked. (like on Help Desk; WIP for notifications)

Even if the automation isn't ready yet, I think the volume of requests isn't too important to be dealt with manually, and it would avoir for these plugins to make another request to add Crowdin integration later.