"trigger" keyword and failing strategy

Summary

Use the trigger keyword as defined here and also set strategy: depend.

This MR implements caosdb/internal/all#650 and caosdb/internal/all#526.

Focus

Is the old functionality reproduced?

Test Environment

Watch the pipelines.

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related issues
• Up-to-date CHANGELOG.md (or not necessary)
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

.gitlab-ci.yml

@@ -109,7 +109,7 @@ trigger_build:
 
   trigger:
     project: caosdb/src/caosdb-deploy
-    branch: $DEPLOY_REF
+    branch: f-trigger-keyword
   # script:
   #   - /usr/bin/curl -X POST
   #     -F token=$CI_JOB_TOKEN