Add the functions of tag automatic scanning and automatic trigger pipeline for gitlab type pipeline under Devops project

1. By default, when you create a pipeline with gitlab type, you can only automatically scan out branches and tags without triggering automatic build

2. There is a requirement that specific branches or tags can not only be scanned, but also be built automatically. It is found that the basic branch build strategies plug-in can solve this problem, but there is no interface for configuration in kubesphere

3. Because there is no interface configuration, you need to configure parameters on Jenkins every time you create a pipeline from kubesphere to realize the function of automatic build

This operation needs to modify the pipeline configuration from kubesphere in the future, and may not be synchronized to Jenkins.

Note:

After the tag is set on gitlab, the CI operation can be triggered immediately to ensure that the online production image can be built. When it comes to the official release, manual CD is to ensure that only CD operation is required to control the online time (CI / CD is a pipeline, and only CI will be triggered automatically through the logic control in jenkinsfile).

The gitlab Branch source plugin is described as follows:

Tag discovery - Discover tags in the project. To automatically build tags install basic-branch-build-plugin.

https://plugins.jenkins.io/gitlab-branch-source/

Start by reviewing the GitLab Branch Source plugin behavior described in the issue and how KubeSphere creates GitLab-type pipelines. Define where branch and tag automatic-build settings belong in the KubeSphere pipeline configuration, and verify that those settings remain synchronized with Jenkins.