F refactor pipe

Summary

Use libraries with versions that have the same branch name than the current version of this repo for tests.

Test Environment

f-test commits

• pylib: ea8c3687
• advanced: 230bab2effe

Pipeline check

• unittests install the correct versions
  • https://gitlab.indiscale.com/caosdb/src/caosdb-crawler/-/jobs/358998#L278
  • https://gitlab.indiscale.com/caosdb/src/caosdb-crawler/-/jobs/358998#L224
• inttests install correct versions
  • https://gitlab.indiscale.com/caosdb/src/caosdb-crawler/-/jobs/359130#L268
  • https://gitlab.indiscale.com/caosdb/src/caosdb-crawler/-/jobs/359130#L262

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 #189 (closed)
• Up-to-date CHANGELOG.md (or not necessary)
• Up-to-date JSON schema (or not necessary)
• Appropriate user and developer documentation (or not necessary)
  • How do I use the software? Assume "stupid" users.
  • How do I develop or debug the software? Assume novice developers.
• 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)
• Appropriate user and developer documentation (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?
• remove f-test branch in caosdb-crawler, caosdb-advanced-user-tools and pylib

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