feat: add teambition plugin

[coldgust]

Summary

All tasks have been completed.

tasks:

• connection and auth
• account corresponding to teambition member
• issue_labels corresponding to teambition tags(标签)
• issue_comments corresponding to teambition task activity(任务动态)
• issue_changelogs corresponding to teambition task activity(任务动态)
• issue_worklogs corresponding to teambition task worktime(任务工时)
• boards corresponding to teambition project(项目)
• board_issues corresponding to teambition project_task
• sprint_issues corresponding to teambition sprint_task
• sprints corresponding to teambition sprints(迭代)
• board_sprints corresponding to teambition project_sprints
• issue_type corresponding to teambition scenario(任务类型)
• issue_status corresponding to teambition taskflowstatus(工作流状态)
• issue corresponding to teambition task(任务)
• blueprint
• e2e test

Does this close any open issues?

Closes #1882

Screenshots

Other Information

After I finish the plugin development, I will also finish the config-ui development.

[likyh]

Hi, Have you finished?

[likyh]

I find timeAfter and iscremental haven't been used correctly.

https://github.com/apache/incubator-devlake/blob/main/backend/plugins/github/tasks/issue_collector.go#L76-L81

We should use like this to support collect after the timeAfter or collect incremently.

If not, we can use normal collector. Or maybe you want to add them next PR?

[coldgust]

Hi, @likyh . Thanks for your review. The PR is finished.
I found that the Teambition api dose not provide date query params. So, I remove that code and use normal collector instead temporarily. If I find the right solution, I will impl it in next PR.

[likyh]

@coldgust Hi there, I have a few questions:

1. I noticed that OrganizationId is only used when collecting accounts. Can we retrieve it after the project collector has run? This would make it easier to support it in config-ui when there is only one ID option available.

2. Are you using it in blueprint advance mode?

3. It seems like all projects are being collected. Shouldn't we only collect what we need? This would make it easier to support teambition in config-ui.

Also, do you have willing to add support for some API in config-ui in the future? (not in this PR)

[likyh]

I have rebased this PR to the latest main. Please pull(rebase) in your local repo.

[coldgust]

Hi, @likyh

1. All teambition api about getting account detail info are need OrganizationId. The project collector api only can get the userIds. But it has a trick to remove OrganizationId param. The TenantId(included in connection info) is equal to OrganizationId, cause teambition only support the organization tenant type. In summary, OrganizationId can get from connection.
2. Yes, I use advanced mode.
3. We can only get the project that correspond to the projectId params.
4. Yes, I am willing to add support for some API in config-ui in the future.

I will add a commit to impl 1 & 3 later.

[likyh]

LGTM, I'll merge it.